STOP-4939 : Added severity for path-declarations-must-exist rule in ruleset package#2907
Open
SB-ChetanKorde wants to merge 13 commits intodevelopfrom
Open
STOP-4939 : Added severity for path-declarations-must-exist rule in ruleset package#2907SB-ChetanKorde wants to merge 13 commits intodevelopfrom
SB-ChetanKorde wants to merge 13 commits intodevelopfrom
Conversation
publishing beta versions for core, cli and rulesets package
remove console logs and checks
SB-ChetanKorde
requested review from
bhaskarsontakke and
prafullaAtSB
and removed request for
SB-dineshbabhale
update test case for - path-declarations-must-exist where it was looking for warning but recent change make it error
pareshb3089
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes #STOP-4939.
Description
The path-declarations-must-exist rule in the OAS ruleset (located at line 332 in index.ts) was incorrectly reporting violations as warnings instead of errors.
Original Behavior
warning path-declarations-must-exist Path parameter declarations must not be empty
This severity level was inconsistent with the rule's intent, which should prevent invalid empty path parameters like /users/{} from being deployed.
Fix Applied
Updated the path-declarations-must-exist rule severity from 0 (hint) to 2 (error) in index.ts:332:
'path-declarations-must-exist': { message: 'Path parameter declarations must not be empty, ex."/given/{}" is invalid.', recommended: true, given: '$.paths', severity: 2, // Changed from: severity: 0 then: { field: '@key', function: pattern, functionOptions: { notMatch: '{}', }, }, },Checklist/Validation
Build all packages
cd /Users/chetannkorde/Documents/Code-Area-51/Spectral-Repo
yarn build
Reinstall spectral-cli globally
npm uninstall -g @stoplight/spectral-cli
npm install -g packages/cli --no-save --force
Does this PR introduce a breaking change?
Screenshots