Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Filter response fields if using JSONAPI Query Parser #120

Closed
jeregrine opened this issue Jun 22, 2018 · 0 comments
Closed

Filter response fields if using JSONAPI Query Parser #120

jeregrine opened this issue Jun 22, 2018 · 0 comments
Labels
enhancement help wanted

Comments

@jeregrine
Copy link

jeregrine commented Jun 22, 2018 •
edited
Loading

Right now we handle the includes case in the query parser but not filtering fields attributes on the response. We can handle this automagically.
@jeregrine jeregrine changed the title Filter response values if using JSONAPI Query Parser Filter response fields if using JSONAPI Query Parser Jun 22, 2018
@jherdman jherdman mentioned this issue Jan 26, 2019
Closed
jherdman added a commit to jherdman/jsonapi that referenced this issue Jan 31, 2019
@jherdman
Fully Support Sparse Fieldsets
7d5cf21 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
jherdman added a commit to jherdman/jsonapi that referenced this issue Jan 31, 2019
@jherdman
Fully Support Sparse Fieldsets
3a37e79 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
jherdman added a commit to jherdman/jsonapi that referenced this issue Jan 31, 2019
@jherdman
Fully Support Sparse Fieldsets
149e44f 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
@jherdman jherdman mentioned this issue Jan 31, 2019
Merged
jherdman added a commit to jherdman/jsonapi that referenced this issue Jan 31, 2019
@jherdman
Fully Support Sparse Fieldsets
c9eb735 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 3, 2019
@jherdman
Fully Support Sparse Fieldsets
c75090c 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 6, 2019
@jherdman
Fully Support Sparse Fieldsets
e6bf362 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 12, 2019
@jherdman
Fully Support Sparse Fieldsets
ebe35a9 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 12, 2019
@jherdman
Fully Support Sparse Fieldsets
381236e 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 13, 2019
@jherdman
Fully Support Sparse Fieldsets
295905c 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 13, 2019
@jherdman
Fully Support Sparse Fieldsets
ae621db 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 13, 2019
@jherdman
Fully Support Sparse Fieldsets
5d662c1 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 17, 2019
@jherdman
Fully Support Sparse Fieldsets
0ddb215 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 17, 2019
@jherdman
Fully Support Sparse Fieldsets
584a3bb 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 18, 2019
@jherdman
Fully Support Sparse Fieldsets
1367099 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
jherdman added a commit to jherdman/jsonapi that referenced this issue Feb 21, 2019
@jherdman
Fully Support Sparse Fieldsets
2667a28 
Whilst the `QueryParser` was correctly identifying requested fieldsets,
nothing was done to actually support this.

This change prunes returned fields to those requested should it be the
case.

Note that this change also includes a few more typespecs for functions I
touched or read.

Resolves beam-community#120
Closes beam-community#156
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeregrine