EntityRef - standardize on PascalCase for entity name and fix minor bug #13631
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.
Overview
Just some cleanup related to EntityRef fields.
Before
EntityRef fields could theoretically accept snake_case or camelCase for the entity name, but they were not very internally consistent and might break with some compound words.
After
Standardize entityRef fields to always use the PascalCase version of the entity. Still accept other formats for legacy reasons.
Technical Details
Also includes a minor bugfix - option lists were not being cached in the entityRef filters, so ajax calls to api.getoptions were being made more often than necessary.