You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whenever there is a field with some additional metadata like "aliases" or "doc" it causes the generated python field to look like this:
However these get ordered behind (original order?) fields with a default value which is not valid python. Without aliases or doc these fields do correctly get shifted before fields with defaults.
Describe the bug
Whenever there is a field with some additional metadata like "aliases" or "doc" it causes the generated python field to look like this:
However these get ordered behind (original order?) fields with a default value which is not valid python. Without aliases or doc these fields do correctly get shifted before fields with defaults.
To Reproduce
Expected behavior
fields get ordered with default values last
The text was updated successfully, but these errors were encountered: