🎨 Palette: Improve JSDoc for comparison methods #816
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improved Developer Experience (DX) by clarifying the behavior of version comparison methods in the JSDoc. Specifically, documented that comparison methods return
falsefor invalid inputs and that theis()method performs a strict string equality check without normalization. This prevents developer confusion regarding edge cases like empty strings orvprefixes.PR created automatically by Jules for task 8226082656635366274 started by @srod
Summary by cubic
Clarified JSDoc for Node version comparison methods to prevent confusion about invalid inputs and strictness. Comparison methods return false for invalid version strings, and is() uses strict string equality without normalizing inputs (e.g., no 'v' prefix handling).
Written for commit d5d0baa. Summary will update on new commits.