close
Skip to content

fix(fix): make --ecosystems case-insensitive#1308

Draft
Martin Torp (mtorp) wants to merge 1 commit intov1.xfrom
fix/ecosystems-case-insensitive
Draft

fix(fix): make --ecosystems case-insensitive#1308
Martin Torp (mtorp) wants to merge 1 commit intov1.xfrom
fix/ecosystems-case-insensitive

Conversation

@mtorp
Copy link
Copy Markdown
Contributor

Summary

  • Lowercase --ecosystems input before validation so NPM, Npm, and npm are all accepted, matching the behavior already in place for --package-managers (feat(fix): add --package-managers flag #1292).
  • Update --ecosystems help text to mention case-insensitivity.
  • Bump patch version to 1.1.93 and add a CHANGELOG entry.

Why

--package-managers was added in #1292 as case-insensitive (input gets uppercased before validation against an ALL-CAPS list). --ecosystems, however, validates input verbatim against an all-lowercase list, so passing NPM would fail with "Invalid ecosystem". Asymmetric UX between two related filters; this commit makes --ecosystems mirror --package-managers.

Test plan

  • New integration test: should accept --ecosystems case-insensitively (passes NPM,PyPI)
  • Existing --ecosystems integration tests still pass
  • Help-text snapshot updated
  • eslint + tsgo pass on the changed files
  • CI green

Lowercase --ecosystems input before validation so values like NPM, Npm,
and npm are all accepted, mirroring --package-managers behavior. Update
help text accordingly and bump patch version.
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.

1 participant