Ability to specify which response model fields to prevent REST resource _over-fetching_ via a query parameter or header

[ghost]

Feature Request

Ability to specify which response model fields to prevent REST resource over-fetching via a query parameter or header

Use case

Third party developers request resources and use only some of the data returned thus discarding unneeded data fields wasting bandwidth, known as the over-fetching problem.

We would then be able to specify the needed fields with either a resource query parameter such as &fields=A,B,C or a header such as x-esi-fields-requested: A,B,C.

This would enable an efficient implementation (no over-fetching) of a REST interface wrapper solution such as proposed in https://github.com/esi/esi-issues/issues/1309

Authentication

Existing authentication is used

Example return

Full or a subset (requested fields) of the data model is returned.

Checklist

Check all boxes that apply to this issue:

• [X] Feature request description is provided
• [X] Use case exists
• [ ] Feature requires a new route
• [X] Feature adds data to existing route
• [ ] Feature requires new auth scope
• [ ] Feature can reuse existing scope
• [ ] Feature does not require auth
• [X] Meta feature, applies to all routes

[ghost]

What is the reason for this ticket being closed?

[DianaOlympos]

Incapability to understand the design of the API and using it, provide nothing to the conversation on top of existing one.

[ghost]

Is there the ability currently to limit the response to a subset of fields that we only need in our apps?

[ddouglas]

No

[ghost]

Then this ticket should be triaged on it's technical and application merit rather than hostility to the ticket creator.