-
Notifications
You must be signed in to change notification settings - Fork 16
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
Include on bigger documents have often problems #114
Comments
Moved to 1.1.0 because this takes more time and 1.0.1 should be released |
There is also a comment inside #90 about those situations. |
Hmm... currently I am having no such problems and I do also not have any example code to correctly reproduce. So decided to move to next milestone. |
Funny : using Version 1.2.0 now and having again such a problem, when switching to
Either it has to do with asciidoctor variant or the adoptions of outdir in execution phase? |
On the other side installed asciidoctor with default options has problems with diagram including! see #161 |
There is still an issue if somebody has multiple document folders, means multiple base dirs. |
Described base dir resolving at https://github.com/de-jcup/eclipse-asciidoctor-editor/wiki/FAQ#base-dir-resolving |
Hmm.. refresh does not rebuild cached base dir completely. |
@vogella Could you do me a favour and checkout 38e7814 - or master HEAD - and test if the includes now working with your documentation setups much more better? There should be no longer any include problems. I tried it with one of my bigger documentation projects and did no longer found any problems - no matter if I am using installed asciidoctor or embedded one, nor if using external or internal previews. Thanx a lot ... |
I don't use the internal build so I don't think I'm a good tester for this. I always build outside of Eclipse via the command line. |
- not very cool solved, but when files are not in current base dir for project they will be rendered just as done formerly. Means of course that maybe images are not correctly shown, but at least content is there. Also users got the possiblity to close all editors open file and do refresh - this will reset the base directory
- cached basedir in provider is also refreshed now - created base class for providers every registered provider is now doing a reset when proviate context reset is triggered
I still have often the problem that includes used in subfiles are not correctly shown.
The mechanism to resolve root dir goes too much deep.
In such a combination e.g. the shared01.adoc has problems, because currently the rootfolder detection
mechanism will go to src/docs/asciidoctor because there is the root for .adoc files
Asciidoc files are always relative to their own position when doing includes. So the resolving of
src/docs/asciidoctor as doc folder will result in problem that the include cannot be rendered by
asciidoctor.
The image mechanism to fetch the root image path etc. is okay. But not this one.
Should have some junit test to prevent those siutations again!
The text was updated successfully, but these errors were encountered: