Allow None Type for Element Properties in _api_generator.py #2145
Conversation
This file contains 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
|
Hey @naaa760 and thank you for your proposal. |
|
Are you still working on this @naaa760 ?
|
|
No activity, closing |
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.
Description of Changes Made to _api_generator.py
Modified create_element_api Method:
Implemented logic to adjust property types, allowing None values to be represented as "none" in the _TYPES dictionary.
This ensures that elements can handle cases where properties may not have a specified type, improving flexibility for developers.
Overall Goal:
Enhance usability by allowing properties without explicit types, preventing potential errors related to type handling during element creation.