1. Please update the icon for ENSApi to use the new ENSApi icon.
2. Please change this text from "Namespace" to "ENS Namespace".
3. Please add an info icon with the following message inside: "This ENS Root Chain RPC is used to power the Resolution API, in situations where Protocol Acceleration is not possible."
4. Please add a COPY (do not move the existing fields under ENSDb!!) of these fields into the highlighted position under ENSIndexer. Therefore, the exact same fields should exist both on ENSDb and ENSIndexer.
5. Please move these fields to the highlighted position. Goal: The "RPC Config" field in ENSApi and the "Indexed Chains" field in ENSIndexer ideally would share the same column alignment in the UI.
6. Please move these fields to the highlighted position. Goal: The "ENS Namespace" fields for both ENSApi and ENSIndexer ideally would share the same column alignment in the UI.
7. Please update the text in this info icon tooltip to the following message: "The ENS namespace that ENSIndexer is operating in the context of."
8. Please move these fields to the highlighted position. Goal: The "Client Label Set" fields in ENSIndexer are directly related to the "Server Label Set" fields in ENSRainbow so it's nice if these fields are located closer to each other.
For background: Please note how we already have blue dashed lines on this page for the purpose of visual storytelling of the ENSAdmin selected connection to ENSNode. No changes to make here. Just flagging the background info.
~Please add similar blue dashed lines between each of the following cards:
- ENSApi to ENSDb
- ENSIndexer to ENSDb
- ENSIndexer to ENSRainbow
Suggest to also increase the vertical spacing between ENSApi / ENSDb / ENSIndexer / ENSRainbow to match the vertical spacing between ENSAdmin and Connection.
This will be nice as it will then achieve visual storytelling of how all of ENSNode's internal services are connected to each other.~
Edit: Please also:
- Verify that all mocks continue working after this change.
- Update the loading state so that we change from 3 to 4 nested loading skeleton panels. This used to be 3, but should now be 4 now that we are introducing ENSApi as a 4th service.
1. Please update the icon for ENSApi to use the new ENSApi icon.2. Please change this text from "Namespace" to "ENS Namespace".3. Please add an info icon with the following message inside: "This ENS Root Chain RPC is used to power the Resolution API, in situations where Protocol Acceleration is not possible."4. Please add a COPY (do not move the existing fields under ENSDb!!) of these fields into the highlighted position under ENSIndexer. Therefore, the exact same fields should exist both on ENSDb and ENSIndexer.5. Please move these fields to the highlighted position. Goal: The "RPC Config" field in ENSApi and the "Indexed Chains" field in ENSIndexer ideally would share the same column alignment in the UI.6. Please move these fields to the highlighted position. Goal: The "ENS Namespace" fields for both ENSApi and ENSIndexer ideally would share the same column alignment in the UI.
7. Please update the text in this info icon tooltip to the following message: "The ENS namespace that ENSIndexer is operating in the context of."8. Please move these fields to the highlighted position. Goal: The "Client Label Set" fields in ENSIndexer are directly related to the "Server Label Set" fields in ENSRainbow so it's nice if these fields are located closer to each other.
For background: Please note how we already have blue dashed lines on this page for the purpose of visual storytelling of the ENSAdmin selected connection to ENSNode. No changes to make here. Just flagging the background info.
~Please add similar blue dashed lines between each of the following cards:
Suggest to also increase the vertical spacing between ENSApi / ENSDb / ENSIndexer / ENSRainbow to match the vertical spacing between ENSAdmin and Connection.
This will be nice as it will then achieve visual storytelling of how all of ENSNode's internal services are connected to each other.~
Edit: Please also: