The general arising Best Practice here is to only pass params (numbers/strings) to link-to/transitionTo
-
-
This forces all paths to go through the model hook; it probably should have been designed that way from the beginning but alas
2 replies 0 retweets 0 likes -
Replying to @amatchneer @machty and
I don't agree with this and I also don't think we should be giving this advice if we're not willing to document it.
2 replies 0 retweets 1 like -
What specifically do you disagree with?
3 replies 0 retweets 0 likes -
Replying to @amatchneer @machty and
I disagree that "only pass strings" is a best practice. Also disagree that we should have done that from the beginning.
3 replies 0 retweets 0 likes -
FWIW I have frequently find people snagged by “why isn’t my model hook being called?” when passing objects into a link-to
1 reply 0 retweets 3 likes -
Replying to @michaellnorth @wycats and
That’s it exactly the issue. The fact that the behavior is so different depending what you pass is not immediately obvious.
1 reply 0 retweets 1 like -
Replying to @mattmcmanus @wycats and
At LinkedIn, the best practice is to always pass an “id” unless there’s a specific compelling reason not to. Cost of confusion is too high
1 reply 0 retweets 0 likes -
Replying to @michaellnorth @mattmcmanus and
If you pass a model you already have ... you don't need to get it again ;) I get the confusion. We should fix.
1 reply 0 retweets 1 like -
Replying to @wycats @michaellnorth and
Right. In hindsight it’s clear. I think what complicated my initial confusion is trying to load/return multiple models with a rsvp hash
1 reply 0 retweets 1 like
I think that is a great point. I don't mean to be such an apologist. @machty is going to write an RFC 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.