Merged
Conversation
Closed
Member
Author
|
For clarity, this PR is in a bit of a weird state. I found specifying columns works fine, except when you choose one which is custom / not part of the model itself. E.g.
Need to upgrade bookshelf & knex and see if the behaviour is still there, and then perhaps raise a bug. |
c56fd8e to
5fda77b
Compare
refs TryGhost#5601, TryGhost#5463, TryGhost#5343 - adds rudimentary support for a 'fields' parameter on browse requests
Member
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 adds a
fieldsparameter to the browse API endpoints. it's super basic - no tests, validation, etc but it works!refs #5601, #5463, #5343
cc @kevinansfield this should be enough to work with for the auto complete :)