Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

KieranLafferty
Copy link

@KieranLafferty KieranLafferty commented Jan 2, 2022

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 🙌

@docs-page
Copy link

docs-page bot commented Jan 2, 2022

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/melos~218

Documentation is deployed and generated using docs.page.

@CLAassistant
Copy link

CLAassistant commented Jan 2, 2022

CLA assistant check
All committers have signed the CLA.

@KieranLafferty KieranLafferty changed the title VSCode project generator script feat: VSCode project generator script Jan 2, 2022
@blaugold
Copy link
Collaborator

blaugold commented Jan 2, 2022

Hey @KieranLafferty, I'm the maintainer of the VS Code extension for Melos. This looks like a feature that might be better implemented there.

@Salakar
Copy link
Member

Salakar commented Jan 2, 2022

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?

@blaugold
Copy link
Collaborator

blaugold commented Jan 2, 2022

We could have a command that when executed:

  • asks for a package,
  • generates a workspace config which contains workspace folders for the package and its dependents,
  • writes that file to a temporary location,
  • opens a new VS Code window with that workspace config.

@KieranLafferty
Copy link
Author

Apologies for the late response here @blaugold @Salakar

Happy to move it over to that VSCode extension. Want me to close this and create a PR there and we can discuss how it integrates on the new PR?

@blaugold
Copy link
Collaborator

blaugold commented Jan 21, 2022

@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.

@KieranLafferty KieranLafferty changed the title feat: VSCode project generator script feat: VSCode workspace generator script Jan 21, 2022
@KieranLafferty
Copy link
Author

Closing this to continue the convo on the other task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants