Feature: ValueOnly Serialiser and Deserialiser#160
Closed
sebbader-sap wants to merge 77 commits into
Closed
Conversation
Offer alternative interpretation on spec
adjust to the correct valueonly format
Contributor
|
This PR is obsolete and has to be replaced by #297 |
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
5 participants
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.
Proposing ValueOnly functionality based on the current model classes. No additional ValueOnly model classes needed but instead introducing Mapper classes.
Deserialisation requires a
normalbase class, as usually a ValueOnly object itself is not enough to have a compliant AAS data object.