You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be useful when navigating large files with lots of exports (read: libraries) to provide a line number for the export as well as file path for the goto function. This might be an editor-breaking change, since the goto response is currently just a string, not an object. We could add another top-level field to avoid the breaking change, but that wouldn't be ideal. Thoughts? I'd be happy to work on this if it sounds useful.
The text was updated successfully, but these errors were encountered:
I like this idea, and I wonder if we could make a cheap test in one of the clients before we try it out? Clients now what variables they go to, and they can make a best-attempt at finding the export in the goto file. If it feels good, we can make it part of the daemon.
It could be useful when navigating large files with lots of exports (read: libraries) to provide a line number for the export as well as file path for the
goto
function. This might be an editor-breaking change, since thegoto
response is currently just a string, not an object. We could add another top-level field to avoid the breaking change, but that wouldn't be ideal. Thoughts? I'd be happy to work on this if it sounds useful.The text was updated successfully, but these errors were encountered: