-
-
Notifications
You must be signed in to change notification settings - Fork 43
Description
As discussed on discord, in v3, the documentation says "Another cool feature is that if the current route already contains the correct dictionary then you do not have to pass a second parameter... [if the route has @id parameter], you can just leave it out completely since the id key is already stored on the request object". The v4 documentation omits that and it doesn't seem to be automatically populating the id as it had previously.
@josephmancuso says
No we didn’t port that over
I removed some of the magic stuff from 3 to 4 to make things clearer
I had lots of people confused about that over the years
If anything that should be noted in the upgrade guide
If it’s missing
There's a section in the upgrade guide for Routes, but it has nothing in it.
Personally, I like the feature when it worked, but it was fiddly and somewhat confusingly described.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status