Add int to defaults too #3
Open
Conversation
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.
Add integer support to Parameter default_value field
Currently, the Parameter.default_value field only accepts Union[str, float, bool], causing integer values like 10 to be converted to 10.0 by Pydantic. This breaks type distinction needed by downstream systems like BIOMERO that generate OMERO scripts requiring correct Int vs Float types.
This PR adds int to the union: Union[str, int, float, bool] for both Parameter and OutputParameter models. The change is backward compatible and enables proper integer/float distinction while preserving existing functionality.