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
Originally posted by alex-pakalniskis April 12, 2024
Problem
When creating a new subgraph using graph init, a user selects the desired protocol network from which to index data.
After selecting the protocol network to index, users are presented with the global list of sub-choices that aren't filtered to the specific protocol network chosen previously.
This is potentially confusing for newer users as "mainnet" could refer to Ethereum mainnet or NEAR/Cosmos mainnet in above figures.
Solution
Filter sub-choices based on selected protocol network, i.e. only show NEAR relevant choices if NEAR chosen, etc.
Clarification
Is the current behavior there for a specific reason? (i.e. some technical requirement)
The text was updated successfully, but these errors were encountered:
Discussed in #1628
Originally posted by alex-pakalniskis April 12, 2024
Problem
When creating a new subgraph using
graph init
, a user selects the desired protocol network from which to index data.After selecting the protocol network to index, users are presented with the global list of sub-choices that aren't filtered to the specific protocol network chosen previously.
This is potentially confusing for newer users as "mainnet" could refer to Ethereum mainnet or NEAR/Cosmos mainnet in above figures.
Solution
Filter sub-choices based on selected protocol network, i.e. only show NEAR relevant choices if NEAR chosen, etc.
Clarification
Is the current behavior there for a specific reason? (i.e. some technical requirement)
The text was updated successfully, but these errors were encountered: