Skip to content

Conversation

@hcharley
Copy link
Contributor

This will help library consumers better integrate semver into their apps.

Possible usecases of consuming this constant:

  • Automatically show a dropdown of available release types that conform to the semver spec
  • Validate user inputs where a release type is expected

...Which will help library consumers better integrate semver into their apps.

Possible usecases of consuming this constant:

- Automatically show a dropdown of available release types that conform to the semver spec
- Validate user inputs where a release type is expected
@hcharley
Copy link
Contributor Author

I am happy to add this to the docs if this idea is approved by the maintainers.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6bc60b7 on charlex:patch-1 into 9f5f615 on npm:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6bc60b7 on charlex:patch-1 into 9f5f615 on npm:master.

@isaacs
Copy link
Contributor

isaacs commented Nov 6, 2019

Yes, please add to the docs, and add at least a basic test. (Just verify it exists and is what you expect; I realize it's kinda silly for such a trivial feature, but it prevents us from accidentally breaking it in the future and not noticing.)

@hcharley
Copy link
Contributor Author

@isaacs I added a section in the README, but it looks like this project as undergone a big change in its structure, and I'm not able to resolve the conflicts right now.

This was linked to issues May 12, 2022
@wraithgar
Copy link
Member

Replaced by #530

@wraithgar wraithgar closed this Apr 4, 2023
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.

https://semver.org/.v2.0.0 require('semver')

4 participants