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
The "Record Resolution Inspector" is live in ENSAdmin at inspect/records.
Currently this route is not "dynamic", in the sense that the name that is having its record resolution inspected is not a dynamic part of the URL.
In PR 1024 a new "Name Details" page is being added to ENSAdmin. An example lookup here can be found at /name/brantly.eth.
This new "Name Details" page introduced the concept of "Actions" to the top breadcrumb / nav bar. Currently the only "Action" available there is to "View in ENS App" that opens an external link to view the related ENS name in the official ENS manager app. Currently this always assumes the mainnet ENS namespace, but a related issue to fix this is here: Use Dynamic ENS Namespace on Name Details Page #1058.
Goals
Make the route in ENSAdmin for inspect/records dynamic, such that the name having its record resolution inspected is always part of the route.
Note: Open to suggestions if we should also make the "Records Selection" a dynamic part of the route as well. My first instinct is to say we shouldn't introduce this capability as part of resolving this issue and instead add dynamic "Records Selection" as a completely separate enhancement.
Support the easy sharing of inspection links that automatically open to the inspection of a specific name.
Add an "Action" to the top breadcrumb / nav bar on the /name route for "ENS Protocol Inspection" that links to the inspect the same name on the inspect/records route.
In the top of the "ENSNode Response" panel on the inspect/records route: add a link to view the profile of the related name on the /name route.
Non-Goals
Suggest not to worry about details such as how these "Actions" appear on mobile. The goal of designing and implementing a nice UI for all variations of this "Actions" bar can be left to a separate issue and is out of scope for this issue.
Background
inspect/records./name/brantly.eth.Goals
inspect/recordsdynamic, such that the name having its record resolution inspected is always part of the route./nameroute for "ENS Protocol Inspection" that links to the inspect the same name on theinspect/recordsroute.inspect/recordsroute: add a link to view the profile of the related name on the/nameroute.Non-Goals