Required file resolver extension point #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
April 7, 2017 09:23
This patch introduces a new extension point which permits expressing custom algorithms for locating files specified with the 'require' statement. Such handlers will be considered first by the 'Open Declaration' functionality which traverses the set of included files when trying to look for a declaration. This allows implementing custom logic for expressions like require customGlobalObject->myLibraryFile; or similar: users can manually evaluate the variable name and return an appropriate File object (or null, if the given string cannot be resolved to any File).
Avoids an 'import' in AbstractOpenDeclaration.
That way the errors are written to Eclipse' workspace log file and show up in the Error Log View in Eclipse itself too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch introduces a new extension point which permits expressing
custom algorithms for locating files specified with the 'require'
statement. Such handlers will be considered first by the 'Open
Declaration' functionality which traverses the set of included files
when trying to look for a declaration.
This allows implementing custom logic for expressions like
require customGlobalObject->myLibraryFile;
or similar: users can manually evaluate the variable name and return an
appropriate File object (or null, if the given string cannot be resolved
to any File).