APIv4 - Fix getFields to respect default_value from getFields #20481
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
A few fixes to make APIv4
getFields
more internally consistent.Technical Details
GetFields had an odd way of setting defaults for field metadata; this reuses the default_value property instead of declaring defaults in an ad-hoc fashion.
Also adds
readonly
to thetable_name
CustomGroup column, since that cannot be changed by the user.