Call for testing: bs-platform@8.4.0-dev.2

[ryyppy]

@BlueHotDog

Looking good, I see that currently the bs-config documentation is missing the pinned-deps and also the schema is missing it

We are literally jumping from dev build to dev build (+ releases), that’s why we missed the timing updating the docs. Build schema was updated today.

[BlueHotDog]

Thanks dude. you’re doing Gods work there… sorry if it sounded like i was complaining, was not, just raised a flag.

[ixzzd]

@Hongbo

Yes, it’s intentional. The thing is that it seems merlin search file by include paths and we treat a package dependency as a black box. However, the original absolute path is encoded in the cmt file, so ideally merlin should be able to find the original path, in that case, we don’t need install those source files

Thanks for the response! Having proper code navigation is a very important part of dev tool, especially if you have a huge codebase. I think most of pinned-packages feature users have pretty complex and big codebase.

What do you think, is the right direction to have fix code navigation in monorepo with pinned packages?

• Should I try to raise the issue in merlin?
• Should I use any other tool for code navigation?

[amiralies]

can you try that situtation with rescript-vscode or vim-rescript?

[ixzzd]

Just made a brief rescript-vscode test, code navigation works fine.
But there is no “reason” file type, I have to specify “ReScript” file type manually to make it work