Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
“Go to Definition” from inside *.ml library file doesn't work
See original GitHub issueFrom a SomeFile.re I can right click -> “Go to Definition” on a standard library function that I use (in this case Format.printf(...)) and it will jump to the definition as I expect (in this case ./node_modules/bs-platform/lib/ocaml/format.ml)
But inside format.ml, “Go to Definition” doesn’t work for me. In this case, in format.ml, printf calls fprintf. When I try to "Go to Definition on fprintf, it says “No definition found for fprintf”
Not sure if this a bug / missing feature? Or I simply miss some settings?
TIA
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I will try to see if I can reproduce it
Can repro. Not sure why. Afaik jump-to-definition requires putting the correct .merlin file at the root of bucklescript’s folder (right now bs ships with a wrong one that contains @bobzhang’s local paths), but that didn’t work either