Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

settings: network preferences #238

Merged
merged 24 commits into from
Apr 8, 2020
Merged

settings: network preferences #238

merged 24 commits into from
Apr 8, 2020

Conversation

rperez89
Copy link
Contributor

@rperez89 rperez89 commented Mar 17, 2020

I created this branch from the court stats one since i needed some stuffs from there, so it will be good to review first #229

Also leaving here a screenshot for further discussions about improvements/changes

Screen Shot 2020-03-17 at 12 55 56 PM

@vercel
Copy link

vercel bot commented Mar 17, 2020

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/aragon/court-dashboard/b290ea0rc
✅ Preview: https://court-dashboard-git-network-preferences.aragon.now.sh

@sohkai sohkai changed the base branch from development to dashboard-stats March 19, 2020 11:57
@rperez89 rperez89 changed the title Network preferences settings: network preferences Mar 23, 2020
@sohkai sohkai changed the base branch from dashboard-stats to development March 29, 2020 22:37
Copy link
Contributor

@sohkai sohkai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a bunch of comments!


return (
<React.Fragment>
<Box heading="Node settings">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a setting for the subgraph API endpoint (and like the ETH node, do some sanity checks against it to make sure it works).

Copy link
Contributor Author

@rperez89 rperez89 Apr 3, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to understand why do we want to let the user change the data source of the dashboard?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case they wanted to run their own hosted instance of the subgraph, just like the ETH node or IPFS gateway.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@sohkai sohkai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple more comments, mostly small ones about style!

Copy link
Contributor

@sohkai sohkai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really like the changes in the last commit!

I'm just concerned about how we're opening the preferences in the global error—perhaps we should spin this topic out into its own PR so we can get this merged sooner than later :).

Copy link
Contributor

@sohkai sohkai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; as discussed offline, let's just remove the button from the global error :).

Copy link
Contributor

@sohkai sohkai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rperez89 rperez89 merged commit 160a3eb into development Apr 8, 2020
@rperez89 rperez89 deleted the network-preferences branch April 8, 2020 23:24
@rperez89 rperez89 mentioned this pull request Apr 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants