-
Notifications
You must be signed in to change notification settings - Fork 4
removed good example from bad example #5
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
hard to tell which example is throwing the compile error Thanks for your project! :)
Ahh, definitely. I think I'd like to show the "good" versions in separate blocks, so I may not merge this... |
.children | ||
[0] | ||
|
||
node | ||
.children | ||
[0] // oops! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have a build running, you might try this and see what you think:
node
.children
[0] // oops!
<!-- -->
node
.children
[0]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this breaks them into separate blocks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing some non-ascii invisible whitespace snuck in there somehow?
Regardless, the <!-- -->
is a separator used for markdown, not something intended to be part of the lightscript. If you look for it in other parts of the file you'll see how it's used
hard to tell which example is throwing the compile error
(hmmm, GitHub diffs are silly sometimes)
Thanks for your project! :)