Support for Serialization, Metadata and Fix for Circular Dependencies #3
Merged
Conversation
…cement function - now it has to have the same number of parameters and the names must match, but the types of the parameters are excluded from the check (for now).
Catch-up with the old repo and minor refactoring.
…ty class methods to shorten the required code generation and also prevent from duplicated serializer and validation objects being created
…ed with metadata. Also refactored the module names.
- refactored the runtime and split the base class and conditions from the utils module - renamed util functions to conform to `rune_...` naming if used by the generator
…eys/references aren't supported yet)
added serialization support for external refs/keys
- renamed all used in the generated runtime functions to be prefixed with rune_
…les. There is still an outstanding issue with the treatment of lists of typeAliases.
# Conflicts: # .gitignore # NOTICE # README.md
implement automated build of the wheel and uploading it as release artefact.
@type/@model generation now compatible with the new generation
added some rudimentary cardinality checks
allow ..WithMeta data types to be initialized with objects of the bas…
fixed the reference resolution issue when deeper nesting was present
…fic meta constraints in _bind_property_to
minor fix to check in addition to _KEY_REF_CONSTRAINTS the type speci…
|
@minesh-s-patel @oblongs @lolabeis I understand this to be important for the serialisation changes. Can you confirm when this will be processed? |
Contributor
|
Please provide release notes for this change. |
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 PR provides support for closing the following Issues in the Rune Python Generator:
Python Generator Should Support Rune Metadata #5
Generated Python code does not support circular dependencies included in Rune definitions #4
Python Generator support for the new Serialization format #3