-
Notifications
You must be signed in to change notification settings - Fork 3
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
Jump to source #4
Comments
this would be a great feature to have! Do you know if we can use ensime to do this? |
I would love an integration with ensime. It probably should be an optional dependency. |
Thanks for the response @bomgar. |
My first idea was to integrate with the ensime-search feature and let ensime display the results. But this is more of a hack. As for the optional dependency part you can have a look at the ensime-helm integration. |
ensime would need a scala source file to be able to correctly know the FQN, but if you know the classname or something you could forward to I don't really know play very well... can you do string based search? You could add a rule for parsing routes strings into ctags if it's regular enough. |
The play routes file compiles to a scala file. Ensime should be able to process this. I don't know if ensime indexes generated sources. |
String based ensime-search is also possible because we know the class and method name in the routes file. This could be good enough. |
Best-effort search on the class name and feeding it into ensime-search sounds like a good starting point. Getting the right class and method without compiling will be pretty hard though because the class can be in a package structure and the method can be arbitrarily nested inside the class (or even imported from somewhere else). Now that I think of it an even better solution could be to |
jump to referenced controller method
The text was updated successfully, but these errors were encountered: