Support both string and integer types for duration in TranslationVerbose #2034
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 update enhances the
TranslationVerbose
model by supporting both string and integer types for theduration
field:duration
field type toUnion[str, int]
to allow both formats.__post_init__
method to ensure consistent handling of integer durations by converting them to strings internally.This change addresses potential usability issues where the duration might be provided as an integer but was previously expected as a string.
Impact: Improves flexibility and usability for the
TranslationVerbose
model.Changes Being Requested
Support for both string and integer values in the
duration
field of theTranslationVerbose
model.Additional Context & Links
This change ensures better compatibility and reduces confusion when
duration
is supplied as an integer.