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.
Hello, as mentioned in #130 , here are some improvements for include system :
The main rationale about it is to also allow some finer control when using core libraries in custom tooling.
Added Include type enumeration
IncludeDirectiveTriviaSyntax gets a boolean "IsLocal"
Pass Include type to both Include Resolver and File System (depending on local flag)
Current file systems and resolver are ignoring flag (so this will not be a breaking change)
Allow to pass our own IIncludeFileResolver to ParseSyntaxTree .
To be allowed to use our own IIncludeFileResolver, we need to provide a source file, so constructor is now public.
I added small tests to verify that syntax flags are correct, and that custom resolver gets called properly.
One discussion part I would have, is that passing IIncludeFileResolver is required, since our include system might not be not file based (zip/resource/memory...) so default resolver will never find the file, and never call the filesystem.
So maybe we should even remove IIncludeFileSystem from the argument list (since resolver should provide it's own file system anyway, or never provide one) ?
Thanks