-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: VSCode workspace generator script #218
Conversation
To view this pull requests documentation preview, visit the following URL: Documentation is deployed and generated using docs.page. |
Hey @KieranLafferty, I'm the maintainer of the VS Code extension for Melos. This looks like a feature that might be better implemented there. |
This would be good, is there perhaps a VS Code Extension API/way of doing this (defining projects) without generating a file? |
We could have a command that when executed:
|
@KieranLafferty No problem :) I've opened a new issue in extension repo (blaugold/melos-code#26), with some thoughts I had. Let's discuss what this feature should do and how to implement it over there. |
Closing this to continue the convo on the other task |
I wrote this script package a while back which generates a VSCode project file out of the dependency tree reported by melos. I've found it pretty useful for larger projects that overwhelm the dart analyzer when too many folders (often unused ones) are open at the same time
Thought I would put this up and see if there's any interest in having such a script in this repo. No worries at all if it's not a good fit.
If there is interest I can spend some time to clean it up a bit and make any changes requested.
Thank you to all who contribute to Melos 🙌