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
{{ message }}
This repository was archived by the owner on Sep 14, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 14, 2026. It is now read-only.
Don't you mean the alias name would end up being field__alias in your example.
It preserves the original field name so that it can be obtained on the response to parse it with this library, with the assumption that the alias is there so the field can be queried more than once.
Activity
dylanahsmith commentedon Dec 22, 2022
Don't you mean the alias name would end up being
field__aliasin your example.It preserves the original field name so that it can be obtained on the response to parse it with this library, with the assumption that the alias is there so the field can be queried more than once.
jens-josh commentedon Jan 4, 2023
If that's by design, then maybe we can have a variant of withAlias that generates the alias as requested?
dylanahsmith commentedon Jan 10, 2023
That would break response parsing, which isn't done with access to the original request.
Do you have an actual use case for being able to avoid the field name prefix?