You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2018. It is now read-only.
It looks like you cannot use withConditions logic with <RelativeFragment> without also including forRoute - the store.matchWildcardRoute will always return null, which means this line always results in a null render.
The 'fix' is to use AbsoluteFragment instead of RelativeFragment, but it would be nice if I could just use one kind of fragment across my entire app without having to worry about different behavior outside of how forRoute is interpreted.
It would be worth adding a parallel test that uses RelativeFragment for both of these test cases, unless RelativeFragment should never be used in this way.
jdmoody, michaelhogg, yacodes, xMartin, kdojeteri and 1 more