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
Currently if you try for example to get output ids, you are able to pass query parameters, which are not supported by design (like querying an address while there are outputs which have no address like alias).
Trying to call such thing will result in a confusing error message:
an indexer API request contains a query parameter not supported by the endpoint: address=snd1zqa0zl20r5w8c5j3m5eqevlw99n8as2at5852xt5mgl8dkvq8dm2y3mlj6e.
This should be handled better by either not being able to pass such query parameters in code such that it throws a compile error
or by sending a more detailed error message which points, that it is not supported for those requests by design.
The text was updated successfully, but these errors were encountered:
Currently if you try for example to get output ids, you are able to pass query parameters, which are not supported by design (like querying an address while there are outputs which have no address like alias).
Trying to call such thing will result in a confusing error message:
This should be handled better by either not being able to pass such query parameters in code such that it throws a compile error
or by sending a more detailed error message which points, that it is not supported for those requests by design.
The text was updated successfully, but these errors were encountered: