[REF] APIv4 refactoring to support calculated fields #20440
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.
Overview
This is a code refactor to make it possible to add ad-hoc fields to the api getfields spec.
Before
All APIv4 fields correspond to db columns for dao entities for the
get
action.After
It's possible to add other fields. They will be ignored by the get api, so handling will need to be done elsewhere.
Technical Details
A big part of this refactor was to move options lookup to a callback function.