Skip to content

Dependencies menu includes dev-dependencies #100

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

Closed
daschl opened this issue Jan 30, 2017 · 3 comments
Closed

Dependencies menu includes dev-dependencies #100

daschl opened this issue Jan 30, 2017 · 3 comments
Labels
A-frontend Area: Web frontend E-easy Effort: Should be easy to implement and would make a good first PR P-low Low priority issues

Comments

@daschl
Copy link

daschl commented Jan 30, 2017

Hi!

I don't know if its intended, but it seems that the dependencies section includes dev-dependencies as well. It is a bit confusing in the sense that one might expect all of these dependencies being pulled in into their project even if thats not the case.

I'd vote to either have two sections (dependencies and dev dependencies) or just to show the regular dependencies in that section. Or maybe add a small "dev" flag to the dev ones?

@crumblingstatue
Copy link

I agree that this is confusing.

For example, it makes it look like byteorder 1.0.0 is depending on unstable 0.x crates, even though those are just dev-dependencies.

@Kixiron Kixiron added the A-frontend Area: Web frontend label May 27, 2020
@Kixiron
Copy link
Member

Kixiron commented May 27, 2020

Triage: This could be fairly easy to do, maybe something to think about as part of #740

@syphar syphar added E-easy Effort: Should be easy to implement and would make a good first PR P-low Low priority issues labels Oct 24, 2023
@syphar
Copy link
Member

syphar commented Oct 21, 2024

dev dependencies are flagged:
Image

@syphar syphar closed this as completed Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Web frontend E-easy Effort: Should be easy to implement and would make a good first PR P-low Low priority issues
Projects
None yet
Development

No branches or pull requests

4 participants