@BastelsBlog https://t.co/dsl3g1Yikr is a thorny one. There is overlapping concepts of workspaces: VS Code multi-root workspace, control repos, multiple modules, etc. Supporting per directory would require the LSP to (IIRC) load puppet-lint for each, which is as difficult as the previous
@timheuer@code Youโll have to ad it to the dependencies section in package.json and include node_modules in the vsix if you want dependencies shipped. Check the .vscodeignore to make sure itโs not in there or else itโs ignored at package time
Twitter is a goldmine for mentors, but only a few women manage to get into the spotlight.
Here are 7 rockstar women in tech, programming, and STEM that deserve your attention (and follow):
@oising +1 on the not copying. For the 'grok' part, we do have 'go to definition' for some of the things you list. What kind of visualization would you be thinking of for examining existing code? Hover over a reference and have it say 'defined in /foo/bar.tfvars'? A graph with nodes?
@oising Not VS Code specific, but towards your project vis: https://t.co/WefEPI7G4z. We've been discussing how to do things like this inside the editor when we get to that stage.
@oising If you have some time, we recently did a live stream about what we've delivered over the last few months. Hopefully some of it is useful to you https://t.co/hmCHSjVfYE