-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug] Cannot read properties of undefined (reading 'shouldSupersede') #20051
Comments
Ouch! Looks like we need more tests here. If you’re able to add some that would help speed up the debugging process. |
The session-kind test expects the PVV Ministerraad to come after the normal Ministerraad in a filtered agendas table. With this new default filtering, we explicitly apply this ordering. An agendaitem delete call was causing errors which might be related to these Ember bugs: - emberjs/ember.js#20051 - emberjs/ember.js#19971 Leaving out setting anchor to null in hope that it might fix it.
We're seeing this in 3.28 fwiw, but the trigger for us is a |
I have the same problem and could solve it by providing For example: <LinkTo @models={{array this.model}} @query={{hash state=@state page=1}}>Label</LinkTo> |
@chriskrycho if i recall it correctly it started with 3.27 and still persists in 3.28 |
Thanks! As with @meirish's bug that's almost certainly a different bug than the one identified in this issue; if you can create a minimal reproduction that would be helpful. Thanks! |
@chriskrycho ah you are right. I'll see what I can do. |
I left a comment suggesting that we might have to revert #19971, but on digging further, I don't think that code path and this one intersect at all. It seems likelier that it's a result of the router.js refactors that landed in between. Investigating that now. |
It is indeed the result of the router.js work; tildeio/router.js#329 introduced a bug which was fixed by tildeio/router.js#334, which we actually have on the beta branch via #20166—I’ve tested that change (by editing |
sweeeeeet! thank you, Chris! ❤️ |
@Turbo87 if you can confirm once Renovate bumps that PR to use 4.7.1, I think we can close this out, as I published 4.4.3 LTS and 4.7.1 stable an hour ago! 🚀 |
I can confirm that CI is green now. thanks again! |
I have just migrated from Ember's Since then, Ember ~5.5.0 stack
Linking #20663, in case its related. |
🐞 Describe the Bug
When calling
routerService.urlFor(...)
the call throws the following error:🔬 Minimal Reproduction
😕 Actual Behavior
The error page does not work properly.
🤔 Expected Behavior
The call does not fail and the error route is displayed correctly.
🌍 Environment
➕ Additional Context
This is most likely related to the changes that were introduced in #19971
/cc @wagenet
The text was updated successfully, but these errors were encountered: