feat!: let .include change the working directory
#266
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, including a file in another directory would not affect the working directory, which was still the caller's.
Now, as it already happens with subdocuments, included files use their own base path.
Consider the tree:
With
main.qd:Previously, in order to access
image.pngfromother.qd:Now, correctly:
This little change brings substantial changes:
.includenow creates aSharedContextwith a modifiedFileSystem, while before it was just using the caller's contextLinkUrlResolverHookupdates the path of affected links, and stores them inResolvedLinkUrlProperty