-
Notifications
You must be signed in to change notification settings - Fork 37
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
Bad path resolution when building an individual files #574
Comments
produces correctly a pdf with corresponding figures. Each chapter contains a figures folder with some figures and such figures are correctly referenced hence found. Here is the contents of
Now
is failing
in the latex the path is
|
Now writing a test showing the problem! |
In transformDocumentFor:
I have a file and we asked to resolve it via the baseDirectory `'/private/tmp/pillardev8InP10/pillar/tests' ^ aPRPDFDocument transformDocument: (self resolveFrom: aPRPDFDocument project baseDirectory asMicResourceReference ) and this part is lost: |
When I do
The bug is showing up In method
because in
there is no reference to Now the PRPDFDocument knows that the file is .... Chapters/Chapter1/chapter1.md
No idea if it works for the index.md |
I think that it was not a regression and that probably I produced chapter via the inputFile in the main.md. I would prefer to have a missing feature over a bug regression. |
Fix is here
|
Next write a nice test!
…compiling-separated-file-httpsgithubcompillar-markuppillarissues574 Fix: #570 and pillar-markup/pillar#574
We face a regression (No this is a regression just a missing feature).
Tested and reproduced in Pillar-dev8, v825, v826, v827 on Pharo 9 and Pharo 10 when compiling an individual files, the containing chapter is not part of the path.
how to reproduce
The text was updated successfully, but these errors were encountered: