OpenAPI Spec contains validation errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- openapi
- Domain
- api
Research direction
Locate the OpenAPI spec file referenced in the issue and paste it into Swagger Editor to reproduce the listed structural errors. Update the named component parameters so the specification validates, then confirm the Apple OpenAPI Swift generator no longer reports the positional path parameter error.
Written by the indexing model from the issue text.
Description
The current OpenAPI specification is not valid and cannot be used in tools like Swagger Editor or code generators.
Steps to Reproduce
1. Open Swagger Editor.
2. Paste the contents of the OpenAPI spec file.
3. Observe the validation errors.
Observed Errors
Swagger Editor reports multiple structural issues:
Errors
Hide
Structural error at components.parameters.comment_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.follower_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.following_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.playlist_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.fake_playlist_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.repost_playlist_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.track_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.test_track_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.user_id
should have required property 'required' missingProperty: required
Jump to line 0
Structural error at components.parameters.user_id_to_follow
should have required property 'required' missingProperty: required
Jump to line 0
The Apple OpenAPI code generator for Swift also fails with similar issues:
- Additional file comments: <none>/Users/obrhoff/Downloads/new_music_app/soundcloud-open-api-schema.yaml: error: Inconsistency encountered when parsing `comment_id` in Document.components.parameters: positional path parameters must be explicitly set to required.
Error: /Users/obrhoff/Downloads/new_music_app/soundcloud-open-api-schema.yaml: error: Inconsistency encountered when parsing `comment_id` in Document.components.parameters: positional path parameters must be explicitly set to required.
[generate] ERROR task failed
- Dominant language
- JavaScript
- Stars
- 253
- Forks
- 53
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from soundcloud/api
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
soundcloud/api#593 · 10 comments ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
soundcloud/api#583 · 1 comment · 1 reaction ·
-
widget
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#557 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
soundcloud/api#548 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#547 · 2 reactions ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
neondatabase/website#6038 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Effect-TS/effect#8728 · 1 comment ·
Maintainers usually reply within 1 day
-
[quality] coverage gate exits 0 when the test run is killed by a signal (tests/tools/coverage-report.mjs:680 `?? 1` is untested)Possibly taken @hivecommons-hive claimed this today. Openagent/quality hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day