Skip to content

fix: registrationId became mandatory on registration response#93

Merged
stroncoso-quobis merged 2 commits intocamaraproject:mainfrom
stroncoso-quobis:81-the-registrationid-field-in-the-regse
Jul 28, 2025
Merged

fix: registrationId became mandatory on registration response#93
stroncoso-quobis merged 2 commits intocamaraproject:mainfrom
stroncoso-quobis:81-the-registrationid-field-in-the-regse

Conversation

@stroncoso-quobis
Copy link
Collaborator

@stroncoso-quobis stroncoso-quobis commented Jul 25, 2025

What type of PR is this?

Add one of the following kinds:

  • bug

What this PR does / why we need it:

As the registrationId is a required element for subsequents actions on the registration management, it is required to ensure that registration creation action includes that regsitrationId on the response.

Which issue(s) this PR fixes:

Fixes #81

Special notes for reviewers:

Solution proposed by @teikuran at scoped issue

Changelog input

 release-note - webrtc-registration
fix: registrationId became mandatory on registration response

Additional documentation

n/a

@stroncoso-quobis stroncoso-quobis added the bug Something isn't working label Jul 25, 2025
@stroncoso-quobis stroncoso-quobis merged commit ecee12c into camaraproject:main Jul 28, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The registrationId field in the regSessionResponse schema required.

2 participants