In extractStrictEntity
also change request to contain that strict entity for inner routes
#961
Labels
help wanted
Identifies issues that the core team will likely not have time to work on
t:routing
Issues related to the routing DSL
t:stream
Milestone
Currently,
extractStrictEntity
runstoStrict
on the request entity and passes it to the inner route. However, if the inner route tries to access the now drained entity again, the route fails. Instead, we can also rewrite the request in the requestContext to contain the now strict entity. This way inner routes can safely access the entity.This doesn't fix #73 (i.e. route alternatives will still fail when accessing the entity) but might still be a user experience improvement.
The text was updated successfully, but these errors were encountered: