-
Notifications
You must be signed in to change notification settings - Fork 11
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
Component not mounted again on route change in choo #22
Comments
hey @yoshuawuyts, sorry to bother... but any suggestions on this? best! |
@dbtek seems like an issue with nanocomponent... a "hotfix" for this, (that worked for me, by now...) would be:
best |
@RafaelAmorim Thanks for workaround. I'll try it! |
We released a new version of nanocomponent yesterday (nanocomponent@next) -
it's got a slightly different API, but we've tried solving all issues that
were plaguing previous versions - perhaps you could give that a try? Cheers!
…On Wed, Jul 19, 2017 at 10:28 AM İsmail Demirbilek ***@***.***> wrote:
@RafaelAmorim <https://github.com/rafaelamorim> Thanks for workaround.
I'll try it!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWleh4naxTUNON8DKPVuZQLJb8bxJ53ks5sPb4bgaJpZM4N5QQ0>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am experimenting microcomponent with choo. Not sure whether I am missing something or not. However, a component inside a route is not visible after one or more route changes.
Reproduce
/about
/
The text was updated successfully, but these errors were encountered: