CLDR-10384 Use display names for Organization menus #2477
Merged
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.
-New cldrOrganizations.js encapsulates org names on front end
-Sort org display names alphabetically on front end with localeCompare
-List Users and Add User menus are alphabetically sorted by org display name
-List Users sections are alphabetically sorted by org display name
-Fix form-validation problems in AddUser.vue, wait until levels and orgs are loaded
-Fix AddUser.vue, clear errors and warnings when Add Another User
-In cldrAccount.js always get orgs; even for a single org, need short/display mapping
-In cldrAccount.js new setMockLevels, setMockOrgs for unit testing without json from server
-In AddUser.java, use Auth.SESSION_HEADER not query param s
-In OrgList.java, respond with both short and display org names
-In OrgList.java, do not share Organization.special (High Coverage and Generated) with the front end
-In UserList.java, do not include org list in json, no longer needed
-Comments
CLDR-10384