-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: make light-js example a proper debugging tool #248
Comments
Here I added the easiest solution for now that just takes the first discovered peer and puts it into the input. This solution should be improved and drop-down can be made out of it. Additionally, I think |
I would rebrand light-js into a debugging tool and redirect developers on other example which have an "app" usage. |
rename to (open to suggestions :P) |
just |
thinking again: |
event better |
then we should extend the example to keep up with the name:
|
I will be taking this on |
Weekly Update
|
Summary
Provide a "combobox" component that allows easily select the target node in https://examples.waku.org/light-js/
Details
The https://examples.waku.org/light-js/ is great indeed! and I use it very often. However, I think it would be great to make it easier to switch among the different known
nwaku
nodes.I suggest having a "combobox/dropdown list" component where the user can easily pick up one of the major
nwaku
nodes.For example, there could be the next values: test-ams; test-us; test-hk; prod-ams; prod-us; prod-hk.
I usually get the underlying multiaddress string from the information given by https://fleets.status.im/ although this is not the best source of this information.
Quotes:
The text was updated successfully, but these errors were encountered: