You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A record with id blahblah69420 doesn't exist! So, I expect pocketbase to return what it usually returns in case of a 404 not found.
However, I get no data in return.
Hm, technically this is working correctly because the fields parameter is a generic way to filter/omit fields from the json response, but I could see why in this case it may not be desired as there is no way to specify upfront what fields for what response should be applied.
With the next release there are plans to add wildcard (*) support and I'll consider skipping the fields transformation for error responses.
Let's say, we have a collection named
users
with data of type:The query
Now, I want to view only the name field of a specific record of
user
collection. So, I queried:A record with id
blahblah69420
doesn't exist! So, I expect pocketbase to return what it usually returns in case of a404 not found
.However, I get no data in return.
Expected data:
Received Data
NOTE
It does not happen if the
field
query parameter is omitted.The text was updated successfully, but these errors were encountered: