Remove focus on input when jumping back#184
Conversation
|
How about this: becomes this: |
|
Yeah i see, makes it definitely more compact and readable. Will change it as soon as i get to it |
|
So I've tried your solution but it didn't quite add up. Just because on the first |
|
My apologies for not reading the original more closely. You could have done something like this to fix it: |
fda2539 to
bd40482
Compare
|
No need to apologize. Thanks for the help, didn't know about the guard clause inside a match arm. Tell me if somethings still not right. I've also just rebased and compressed to one commit |
Rigellute
left a comment
There was a problem hiding this comment.
Sorry for the delay in respoding @TheWalkingLeek.
Good work! Thank you for the contribution 👍
|
@all-contributors please add @TheWalkingLeek for code |
|
I've put up a pull request to add @TheWalkingLeek! 🎉 |
…n-back Remove focus on input when jumping back
This is fixing #174
First of all I wanted to say that I'm pretty new to Rust so if you notice anything and have tips for me please feel free to share them with me :)
Also I realized that if the first action is to use the input field (thus the second route in the
navigation_stackbeing a route with the idSearch) theHomeroute will not be shown on navigating back because the second route will be popped in the match I've added and theis_none()check will break after...I didn't know how to prevent this effectively without slaughtering the code. So any ideas would be really appreciated.