feat: make state optional for job orders#743
Merged
anonymoususer72041 merged 1 commit intoMay 13, 2026
Merged
Conversation
anonymoususer72041
force-pushed
the
feat/joborders-state-optional
branch
from
98549db to
bbfac39
Compare
anonymoususer72041
force-pushed
the
feat/joborders-state-optional
branch
from
bbfac39 to
2749c6d
Compare
anonymoususer72041
force-pushed
the
feat/joborders-state-optional
branch
from
2749c6d to
d9ea826
Compare
anonymoususer72041
force-pushed
the
feat/joborders-state-optional
branch
from
d9ea826 to
ac8eabe
Compare
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
1 participant
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.
Summary
This PR makes the
statefield optional when creating and editing job orders.This change removes the required marker from the job order add and edit forms, drops the client-side validation that forced a state value and updates the server-side validation so job orders can be saved without a state.
Motivation
OpenCATS is being improved for better internationalization.
Requiring a state works for some countries, but it does not fit well everywhere. In many countries, a state or equivalent administrative region is uncommon, not normally used in job postings or not expected as part of a business address. Making this field optional allows job orders to better reflect local conventions and avoids unnecessary validation failures for users outside state-centric address formats.