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

[Feature] Add --dev flag if dependencies can't be found #253

Open
mrcjkb opened this issue Apr 7, 2024 · 1 comment
Open

[Feature] Add --dev flag if dependencies can't be found #253

mrcjkb opened this issue Apr 7, 2024 · 1 comment
Labels
enhancement New feature or request needs-triage

Comments

@mrcjkb
Copy link
Member

mrcjkb commented Apr 7, 2024

Some non-dev rocks might have dependencies listed that only exist in the dev manifest.
It might be a good idea to check install errors for dependencies not being found, and re-run with --dev.

I'm not 100 % sure how I feel about this. Ideally, rocks that depend on something unstable shouldn't have stable releases.

@mrcjkb mrcjkb added enhancement New feature or request needs-triage labels Apr 7, 2024
@mrcjkb
Copy link
Member Author

mrcjkb commented Apr 7, 2024

I'd propose YAGNI for now.

For reference: This would allow plugins that depend on other plugins that only have an scm release to have a SemVer version.
sindrets/diffview.nvim#320

The question is, should plugins that have unstable dependencies have unstable releases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant