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 has been archived by the owner on Apr 4, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
In order to reduce nameservice lookup attempts for unsupported protocols, Mailchain introduced nameservice flags on the /protocols endpoint see mailchain#640:
Describe the solution you'd like
Add support for this feature in the Mailchain inbox so lookups do not occur unnecessarily.
Describe alternatives you've considered
Requesting Mailchain backend to handle the logic- this could be done at a later stage, but the current proposed fix is sufficient
The text was updated successfully, but these errors were encountered:
* Fix typo in error message
* update angular cli
* update protocols response
* add local-storage-nameservice service
* add getProtocolNetworkAttributes to be used for any attribute for a protocol network
* Add methods to inbox for nameservice settings
* handle observable and awaits for resolving names
* add more async calls to tests
add conditional logic for calling resolveName and resolveAddress
* fix test
* clear sessionStorage before each test
* fix tests
* temporary test fix (see #217)
* fix tests by adding protocols stub
Is your feature request related to a problem? Please describe.
In order to reduce nameservice lookup attempts for unsupported protocols, Mailchain introduced nameservice flags on the
/protocols
endpoint see mailchain#640:Describe the solution you'd like
Add support for this feature in the Mailchain inbox so lookups do not occur unnecessarily.
Describe alternatives you've considered
Requesting Mailchain backend to handle the logic- this could be done at a later stage, but the current proposed fix is sufficient
The text was updated successfully, but these errors were encountered: