Fix response payload type for PutSubmodelById#615
Open
aaronzi wants to merge 1 commit into
Open
Conversation
…turns a Submodel instead of a Reference
mjacoby
approved these changes
May 21, 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.
This pull request fixes the response payload type for the
PutSubmodelByIdoperation in the Asset Administration Shell Repository OpenAPI specification. Specifically, when a submodel is created (status code 201), the response now correctly returns aSubmodelobject instead of aReference. The changelog has also been updated to reflect this fix.API Specification Fixes:
AssetAdministrationShellRepositoryServiceSpecification/V3.1_SSP-001.yamlwas updated to clarify that a submodel is created, not a reference.Submodelinstead of aReferencefor thePutSubmodelByIdoperation.Documentation Updates:
changelog.adoc) now documents this fix under minor changes, referencing the related issue.Related Issue
See #601