Repository navigation
Set aas-core-codegen to 0.0.27rc5 and meta 796ae74 - #6
Merged
Merged
Conversation
We update to aas-core-codegen 0.0.27rc5 and to the latest aas-core-meta 796ae74, and re-generate the code. The meta-model file itself is pinned to 543f3c0, the last commit which changed ``v3_2.py``. The relevant changes are: * JSON-able values admit JSON null (``None``) at any depth ([aas-core-codegen#873], [aas-core-meta#416]), *e.g.*, for an empty element of a submodel element list in the ValueOnly JSON. An optional JSON-able property holding a null counts as absent. In XML-RPC, a null is written as ``<nil/>``. * The results of ``GetSubmodelsValueResult`` and ``GetSubmodelElementsValueResult`` are arrays of ValueOnly JSON objects instead of a single JSON object ([aas-core-meta#415]). We deviate from the OpenAPI since V3.0.4 ([aas-specs-api#414]), which we suspect to be buggy, and follow [BaSyx Go] and the prose of the specification. [aas-core-codegen#873]: eclipse-aascw/aas-core-codegen#873 [aas-core-meta#416]: eclipse-aascw/aas-core-meta#416 [aas-core-meta#415]: eclipse-aascw/aas-core-meta#415 [aas-specs-api#414]: admin-shell-io/aas-specs-api#414 [BaSyx Go]: https://github.com/eclipse-basyx/basyx-go-components
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.
We update to aas-core-codegen 0.0.27rc5 and to the latest aas-core-meta 796ae74, and re-generate the code. The meta-model file itself is pinned to 543f3c0, the last commit which changed
v3_2.py.The relevant changes are:
JSON-able values admit JSON null (
None) at any depth (aas-core-codegen#873, aas-core-meta#416), e.g., for an empty element of a submodel element list in the ValueOnly JSON. An optional JSON-able property holding a null counts as absent. In XML-RPC, a null is written as<nil/>.The results of
GetSubmodelsValueResultandGetSubmodelElementsValueResultare arrays of ValueOnly JSON objects instead of a single JSON object (aas-core-meta#415). We deviate from the OpenAPI since V3.0.4 (aas-specs-api#414), which we suspect to be buggy, and follow BaSyx Go and the prose of the specification.