Fields array refactor #96
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r's metadata idField='OBJECTID', add a seperate OBJECTID field object to the fields array of the response.
dmfenton
approved these changes
Apr 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This new implementation supports using a provider's
idFieldfrom metadata as the source of the OBJECTID field's value. The field referenced byidFieldis maintained in thefieldsarray of both query and layer services. Support is removed for using a field without name or alias of 'OBJECTID' as the OBJECTID field - which produces buggy behavior in ArcGIS clients.In addition, log warning are added when an
idFieldis not set, or its key/values are potentially problematic in ArcGIS clients.