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.

Sign up for GitHub

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

Jump to bottom

Settings component that allows customising RPC/API endpoints, etc. #83

Open
faddat opened this issue Jan 24, 2021 · 5 comments
Open

Settings component that allows customising RPC/API endpoints, etc. #83

faddat opened this issue Jan 24, 2021 · 5 comments
Assignees
@marinhoarthur
Labels
feature-request A new feature implementation is wished

Comments

@faddat
Copy link

faddat commented Jan 24, 2021

Screen Shot 2021-01-25 at 5 23 48 AM

Select the RPC node:

Screen Shot 2021-01-25 at 5 24 45 AM

I reckon:

For now we give this the sanest default possible and provide a place for the user to enter the URL. Will work nicely with new GH pages auto-deploy.

User can have a pi at splash.local, enter splash.local and their browser will access that rpc from github pages.

Pattern also allows for mass experimentation with front ends.
@faddat faddat self-assigned this Jan 24, 2021
@faddat
Copy link
Author

faddat commented Jan 25, 2021

https://youtu.be/B2z6uZjJ1P8

@fadeev
Copy link
Contributor

fadeev commented Jan 25, 2021

Yes, this will come once we update the frontend. We're working on it 🙂

@fadeev fadeev transferred this issue from ignite/cli Apr 9, 2021
@fadeev fadeev changed the title vue: RPC Selection Settings component that allows customising RPC/API endpoints, etc. Apr 9, 2021
@clockworkgr
Copy link
Collaborator

Vuex already supports this.. just a question of adding the selection dropdown

@Osub
Copy link

Osub commented Jul 29, 2021

me too

@marinhoarthur marinhoarthur added the feature-request A new feature implementation is wished label Nov 23, 2021
@marinhoarthur marinhoarthur assigned marinhoarthur and unassigned faddat Feb 2, 2022
@marinhoarthur
Copy link
Contributor

update:

  • closed once next major is published

@marinhoarthur marinhoarthur added the closed-after-next-major Already solved by SF 1 but not published yet. label Feb 2, 2022
@marinhoarthur marinhoarthur removed the closed-after-next-major Already solved by SF 1 but not published yet. label Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marinhoarthur marinhoarthur

Labels
feature-request A new feature implementation is wished
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fadeev @marinhoarthur @clockworkgr @faddat @Osub