Skip to content

Conversation

@jjjasper
Copy link
Collaborator

Fix for #242

Improve the error message when the api version in the file cannot be parsed.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

Copy link
Contributor

@bartveenstra bartveenstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this allowed? 1.0.0-alpha

Copy link

@BB-DDeChristofaro BB-DDeChristofaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the new error message! Thank you!

@jjjasper
Copy link
Collaborator Author

Is this allowed? 1.0.0-alpha

The code validates the version number only to the extend of being able to deduct what is the major so it can compare that it matches the version in the filename.
Full validation should be part of linting.

@bartveenstra bartveenstra merged commit 9ab36ed into main Nov 16, 2021
@santam85 santam85 deleted the fix/242-proper-error-message-on-invalid-version branch July 6, 2022 13:51
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.

Error messages need more description when versions do not match

4 participants