-
Notifications
You must be signed in to change notification settings - Fork 195
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
fix(kollider): routes #2309
fix(kollider): routes #2309
Conversation
🚀 Thanks for the pull request! Here are the current build files for testing: Download and unzip the file for your browser. Refer to the readme for detailed install instructions. This build is brought to you by: Want to sponsor the next build? send some sats to ⚡️builds@getalby.com (don't forget to provide your name) Don't forget: keep earning sats! |
Thanks for the PR, but this change makes Also I am not able to reproduce the issue mentioned here: #2250 (comment) cc @reneaaron |
Here is a video displaying the steps to reproduce and the clicks: Kollider-routes.webmBasically, it is :
I was able to reproduce it on the master branch for both Brave, Chrome and Firefox. With node versions |
nope, since there is an "index" child |
@im-adithya could you please explain what the cause of the bug was and what the reasoning behind the solution is. These changes will cause merge-conflicts with #2272 that I'm working on. |
My commit basically adds recursive looping for those routes instead of the hardcoded mapping (which assumes one child at max) and also expects the parent to have an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
Describe the changes you have made in this PR
Kollider wallet variants (buttons signup and login) were not working as expected.
Link this PR to an issue [optional]
Fixes #2355
Type of change
(Remove other not matching type)
fix
: Bug fix (non-breaking change which fixes an issue)feat
: New feature (non-breaking change which adds functionality)feat!
: Breaking change (fix or feature that would cause existing functionality to not work as expected)docs
: Documentation updateScreenshots of the changes [optional]
Add screenshots to make your changes easier to understand. You can also add a video here.
How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist