Repository navigation
Rename API to device-media-streaming-rate - #50
Merged
Merged
Conversation
Align the API name with the repository name (#38): - API definition file renamed to device-media-streaming-rate.yaml - info.title, tags, servers.url, security scope, schema names and description references updated accordingly - Test definitions renamed to device-media-streaming-rate.feature with matching resource path and scenario tags release-plan.yaml is updated in a separate PR, as the validation rules require release-plan changes to be in their own PR.
CAMARA Validation — FAIL1 errors, 1 warnings, 1 hints | Profile: standard |
Contributor
Author
|
please note: Requesting a review and approval for this PR. @Kevsy @sachinvodafone |
Kevsy
approved these changes
Oct 16, 2026
Kevsy
left a comment
Kevsy
left a comment
There was a problem hiding this comment.
LGTM, noted regarding the validation warning paradox.
sachinvodafone
approved these changes
Oct 16, 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
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.
What type of PR is this?
What this PR does / why we need it:
Aligns the API name with the repository name, as requested in #38:
device-media-streaming-rate.yamlinfo.title→ Device Media Streaming Rate; tags,servers.url({apiRoot}/device-media-streaming-rate/vwip), security scope, schema names and description references updated accordinglydevice-media-streaming-rate.featurewith matching resource path and scenario tagsThis is a pure name substitution on top of #47; no other content changes.
Which issue(s) this PR fixes:
Fixes #38
Special notes for reviewers:
release-plan.yamlnames the new API. The release plan update (r1.2 rc on Commonalities r4.4,api_name: device-media-streaming-rate) follows in a separate PR, since release plan changes must be in their own PR. Neither PR validates green while the other is unmerged, so they need to be merged one right after the other.media-streaming-ratefor the published r1.1 alpha. That section is maintained by the release automation and is correct for that release.code/commonsync for r4.4, then the switch to the r4.4 error catalogue with the 422/429 test scenarios.Changelog input
Additional documentation