Acknowledged
4 months ago

bug: go to definition / references stopped working in VSC extension 1.1.1 in SDK 8.1.0

Most of the "click" actions that worked until 1.1.0 (in SDK 7.3.4) stopped working. In the past I could click on a function and it took me to the function definition, or I could click at the function name in the definition and it opened a list of the references and I could choose one and go there. This (and probably other similar functionalities) work no more in Monkey C VSC extension 1.1.1, SDK 8.1.0

see: https://forums.garmin.com/developer/connect-iq/f/discussion/405971/monkey-c-vscode-extension-cmd-click-to-open-documentation/ 

flocsy🤠
  • 4 months ago

    Thinking about it, if you're not seeing links/goto definition/goto references where you used to (as provided by prettier-monkeys), maybe there's some new feature that you're using that my extension doesn't recognize, which could be breaking the analysis for the entire project (we've seen that before with changes to the jungle for example).

  • 4 months ago

    I'm a bit confused...

    Garmin only added goto definition/goto references in 8.0.0 (and it didn't work very well, and still has bugs in 8.1.0). My extension has been providing that functionality for years, and it still works for me - although in some cases you get two listings for everything, because both extensions provide the same info.

    I've tried turning my extension off to see how well Garmin's new functionality works, and it's pretty hit or miss. Sometimes it finds a definition, and sometimes it doesn't.

    So I agree it's buggy, but I don't think it's stopped working; it's gone from not existing at all, to partially working...

  • 4 months ago

    In the past I could click on a function and it took me to the function definition, or I could click at the function name in the definition and it opened a list of the references and I could choose one and go there.

    This was 's "Prettier Monkey C" plugin functionality. AFAIK, prior to SDK 8 Garmin's "Monkey C" plugin was a project manager, debugger and a primitive tokenizer for code colorization with color schemes without any code analysis.

    How MC and PMC will coexist now to not interfere each other in overlapping functionalities (showing hints, going to references, ...)? That's a good question.