-
Notifications
You must be signed in to change notification settings - Fork 38
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
small quirk when using import and continue together #82
Comments
just incase anyone is disparate to make both work, i hacked around it buy moving .... Line 263 in 1ea68ad
to line 22 instead
As i didn't bother to read more than 8 lines of code, i wont be presumptuous and raise a pull request. I'll leave that for someone that knows what they are doing 😁 |
seems to work great. There are other ways to do this (could check to see if the var exists before declaring it and then leave it in the same spot). Anyhoo, have put up a pull to move it to the beginning of the file. Feel free to reject. Again - thanks for the fantastic tool! |
Wow - love your work. Having heaps of fun using it. A great tool.
Thought i'd point this out as i came across it. Its not a big deal, but it gets a bit confused when you use both import and continue. Heres what i think is happening. after compile, in the second file, it resolves to the same label for the data-section as the first file
<a class="squiffy-link link-section" data-section="_continue1" role="link" tabindex="0">but if i use continue</a>
heres an example ...
file1.squiffy
file2.squiffy
anyway - not a big deal. Just thought i'd point it out. Can always use
[[some other section]]
as a workaround.Thanks for the fantastic tool !
The text was updated successfully, but these errors were encountered: