chore(platform): Extend worker interfaces for batch operations #2419
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds batch interfaces and leverages them for specific "hot paths". The following now have batch variants that take an array of the same type as the non-batch variant.
getAddressProfile()
findNode()
getAppPublicProps()
To get around our previous design choice of having an
AddressURN
be needed for the construction of the Address client, this also introduces a no-op placeholder AddressURN that can be used to initalize a client, so that the batch interfaces (with multiple AddressURNs) can be leveraged.Also removes ENS lookups for smart contract wallets, due to the worker subrequest multiplication for contract addresses.
Note:
getAuthorizedAppScopes()
will get addressed as part of bigger effort under #2013Related Issues
Testing
Checklist