-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement fields extension #709
Comments
Follow up to #707 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improvement
For debugging and for environments where shipping a lot of extra JSON is costly (bandwidth-constrained environments, workflows where you might want enough items that the extra time / bandwidth adds up to significant overhead), it would be good to be able to limit the fields returned in search with the fields extension. The
fields
extension has some pretty straightforward semantics and is allowed to break the promise that search returns valid items (or even valid geojson), so it should be doable with JSON-only operations applied to the search result.The text was updated successfully, but these errors were encountered: