Support projections (field allowlist) in entity queries about chiselstrike HOT 5 OPEN

As a followup thought, it would be interesting to see how this could apply to the generated TS library. Could the specification of fields also omit object properties from the returned result type of queries?

from chiselstrike.

Just to clarify, you are talking about CRUD API, aren't you?

from chiselstrike.

Yes, just the generated API and not for other routes in general.

from chiselstrike.

Ok. In that case, it sounds fairly easy to do.
One thing though, why do you want the ID to be always present if user doesn't specify it? I know it's sort of a special field, but if user doesn't want it, why send it? 🤷‍♂️

from chiselstrike.

I'd consider it a best practice to always send the ID. After all, a set of results that's completely void of properties would be confusing (even if that's what they asked for) and impossible to know how to compose more URLs to get the full data for individual items if desired.

As a specific example, let's take PUT, which generates an ID. If the developer wishes to not get reflected back to them all the properties that they just specified, they would at least need the ID to get a hold of it later. Not sending it might be a confusing mistake.

from chiselstrike.