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.
I checked that fieldType: integer with a number array value should never exists
(afaict) by adding all possible number fields in our test account to our
"Test Entity" entity type, hitting composeAbstractSchema, and checking that
type.integer was not present for any list types.
When you add a custom field, if you make it a number of list of number field,
the field type will be a "decimal" type not an "integer". (I am probably not
using terminology in an exact manner here).
J=SLAP-2314
TEST=manual
tested that I can get back an integer direct answer using the "oliver shi pool count?" query