feat(engine): support go to definition when function defined in __using__ #1
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 complements katafrakt/elixir_sense#1 by un-skipping the existing test and adding one more case, which I did not cover initially.
It add working go-to-definition for situations, when a function is defined by a macro in its
__using__, for example:When editor invokes go-to-definition in the place marked by a pipe, it will go to
Ecto.Repo's source file to the line defining theallfunction.Similarly, when we have
MyApp.Repo.al|l(Thing), it will jump to the same place in theEcto.Repo's source file.