Skip to content

feat(#46): Add a flag for looking at dev-dependencies as well#169

Open
mstrydom wants to merge 1 commit intobnjbvr:mainfrom
mstrydom:main
Open

feat(#46): Add a flag for looking at dev-dependencies as well#169
mstrydom wants to merge 1 commit intobnjbvr:mainfrom
mstrydom:main

Conversation

@mstrydom
Copy link

This commit adds a naive implementation for looking at dev-dependencies. Its added as a flag, since it is a change it behaviour.

This does not do anything fancy in terms of new search locations and smart classifications on location. It will also not let you know if a dependency can be moved from the main section to the dev section, but that could be a nice extension.

Issue: #46

This commit adds a naive implementation for looking at dev-dependencies.
Its added as a flag, since it is a change it behaviour.

This does not do anything fancy in terms of new search locations and
smart classifications on location. It will also not let you know if a
dependency can be moved from the main section to the dev section, but
that could be a nice extension.

Issue: bnjbvr#46
@mstrydom
Copy link
Author

This is a naive implementation for #46 . There are some option issues I would like guidance on from the maintainers:

  1. I added a flag to start looking at dev-dependencies and wired it up for both --with-metadata and without. I think in --with-metadata mode, I might actually be regressing, as I think it was already looking at dev-dependencies and I am now removing them.
  2. I am not doing any smart "per location" searching. This is mainly since it looked like machete already just searches everywhere.
  3. Any more testing that can be suggested?

@mstrydom mstrydom marked this pull request as ready for review May 19, 2025 19:48
@mstrydom
Copy link
Author

Another thing I am wondering is whether I should not add build dependencies while I am here? Maybe the flag should then just be --check-all-dependency-types ?

@mstrydom mstrydom marked this pull request as draft May 20, 2025 02:15
@mstrydom mstrydom marked this pull request as ready for review May 20, 2025 02:15
@mstrydom
Copy link
Author

@bnjbvr Pending review

@bnjbvr
Copy link
Owner

bnjbvr commented May 25, 2025 via email

@mstrydom
Copy link
Author

mstrydom commented May 27, 2025

As a result, please avoid review pings. If you plan to pay me for working on this, I'd be happy to set up some consultancy contract.

My apologies. I just was not sure if something needed to be done to get it on your radar (edit: or anyone else with the right permissions/ownership). Please let me know if there is anything I can do to reduce the time burden on you.

@bnjbvr bnjbvr self-requested a review August 1, 2025 13:11
@nejcgalof
Copy link

A gentle reminder that the feature is wanted and the MR has been open for quite a long time.

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.

3 participants