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
Make the x/metadata queries only return the entry/entries requested, without extra info.
Problem Definition
Currently, the metadata queries put each result in a wrapper that also has address info. Those address info chunks add quite a bit of data to the results. That extra data becomes problematic with smart contracts. Including the request in the response is similarly problematic.
Proposal
Only optionally include the request in the responses and default to not including them.
Only optionally include the id info in the responses and default to not including them. When not including id info, the entries will still be in a wrapper, but the id info fields will be nil. Handling of not-found entries should remain the same (i.e. add a wrapper entry with id info of the thing not found).
Create a new GetByAddr endpoint that takes in one or more metadata addresses and returns all that are requested. This should NOT be able to include the request or id info, just the data requested. The response will need to have a list of each of the 6 metadata types as well as a list of "not found" addresses. Either the entry goes in it's appropriate list or else the address is added to "not found."
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
Make the
x/metadata
queries only return the entry/entries requested, without extra info.Problem Definition
Currently, the metadata queries put each result in a wrapper that also has address info. Those address info chunks add quite a bit of data to the results. That extra data becomes problematic with smart contracts. Including the request in the response is similarly problematic.
Proposal
GetByAddr
endpoint that takes in one or more metadata addresses and returns all that are requested. This should NOT be able to include the request or id info, just the data requested. The response will need to have a list of each of the 6 metadata types as well as a list of "not found" addresses. Either the entry goes in it's appropriate list or else the address is added to "not found."For Admin Use
The text was updated successfully, but these errors were encountered: