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
{{ message }}
This repository was archived by the owner on Jul 13, 2025. It is now read-only.
For "applicant_marital_status" which is a categorical value, we have multiple choices (implemented via Enum). Due to weird reasons, I have to modify pydantic Payload validation to accept both Enum name (str) and values (int).
To include the ability to accept an integer for each state, for some reason, I caused a bug in the original string based value for "applicant_marital_status". For example:
Now (reversed): "applicant_marital_status": "married" ❌ | "applicant_marital_status": "5" ✔.
This needs to be fixed asap as the front-end website uses the string behavior, and we must keep backward compatibility in the APIs.
Remark
The reason we must keep backward compatibility in the APIs is that in beta stages there should be less API change for front-end so they can focus on UX as the current UX is terrible.
Intro
For
"applicant_marital_status"which is a categorical value, we have multiple choices (implemented viaEnum). Due to weird reasons, I have to modify pydanticPayloadvalidation to accept bothEnumname (str) and values (int).To include the ability to accept an integer for each state, for some reason, I caused a bug in the original string based value for
"applicant_marital_status". For example:"applicant_marital_status": "married"✔ |"applicant_marital_status": "5"❌."applicant_marital_status": "married"❌ |"applicant_marital_status": "5"✔.This needs to be fixed asap as the front-end website uses the string behavior, and we must keep backward compatibility in the APIs.
Remark
The reason we must keep backward compatibility in the APIs is that in beta stages there should be less API change for front-end so they can focus on UX as the current UX is terrible.