-
Notifications
You must be signed in to change notification settings - Fork 132
@component: Bad character escape sequence error on windows 10 #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
DoubleU23
added a commit
to DoubleU23/better-docs
that referenced
this issue
Dec 7, 2019
DoubleU23
added a commit
to DoubleU23/better-docs
that referenced
this issue
Dec 7, 2019
DoubleU23
added a commit
to DoubleU23/better-docs
that referenced
this issue
Dec 7, 2019
I can confirm that fix from DoubleU23 is working. |
I still get the issue using "better-docs": "1.4.7" on Windows 10. Looks like the pathing to the component is erroneous. Here is the interesting part of the stack trace:
|
The fix from DoubleU23 has not been implemented. Would be nice to get this in. |
Please we need this! |
wojtek-krysiak
pushed a commit
that referenced
this issue
Apr 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I add the tag @component in a React functional component description header and I ran the documentation generation I am getting the following error. Any idea of how the generated PATH got inserted
\
in itThe text was updated successfully, but these errors were encountered: