Remove Level from /$metadata#250
Remove Level from /$metadata#250sebbader-sap merged 3 commits intoIDTA-01002-3-0_bugfix-2-preparationfrom
Conversation
BirgitBoss
left a comment
There was a problem hiding this comment.
It seems to me that https://app.swaggerhub.com/apis/Plattform_i40/SubmodelServiceSpecification/V3.0.2_SSP-001#/Submodel%20API/PatchSubmodelElementByPath-Metadata still has Level as parameter
|
SwaggerHub is not synched yet. Will do after this and a few other OpenAPI-related PRs are merged. |
same for .yml I would say |
|
@BirgitBoss I just did a detailed review and could not find anything wrong in the *.yaml files. If you still think there is something wrong, please provide an inline comment at the concrete position, otherwise update your review to "accept" so that @sebbader-sap can merge |
BirgitBoss
left a comment
There was a problem hiding this comment.
did not find any errors
* fix metadata and path endpoints * increase the version to the v3.0.2 bugfix version * remove bytes * remove "submodelElements" from SubmodelValue * Replace Service Description Profiles Enum with an open List (#230) * change servicedescription/profiles enum to an open list, providing predefined values only as examples * Remove Level from /$metadata (#250) * remove the Level modifier from $metadata requests * remove allOf SubmodelElementAttributes from SubmodelElementMetadata * fix ValueOnly description * PathItem Fix (#262) add array<pathitem> where missing + new pathitem regex * fix the regex pattern for part 2 classes according to the JSON schema regex (#256) * fix bugs in the valueonly classes * change annotations from array to value only * replace regex patterns with latest json schema v3.0.1 content * using the new string regex pattern also for part 2 classes --------- Co-authored-by: Alexander Gordt <100141498+alexgordtop@users.noreply.github.com>
Solves #249