APIv4 - Fix nonstandard camelCase of title_plural field #18873
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
In a feature recently added by @agh1 and myself, the api returns the name of each entity in plural form as
titlePlural
. However, api output by convention does not use camelCase. This fixes it, adds the field to the api spec, and backports the test from master with the updated case.Before
Api returns
title
andtitlePlural
for each entity.After
Api returns
title
andtitle_plural
for each entity.Comments
There may be a conflict in forward-merging this to master. I'll fix that when we merge this.