Replies: 5 comments
-
@ry Currently, there is no public API available to directly test the handler with Routerify's request data. To address this, we can propose two possible approaches: Approach 1: Expose
|
Beta Was this translation helpful? Give feedback.
-
@rousan I concur. |
Beta Was this translation helpful? Give feedback.
-
You can always set your data container as something like In either case this is a niche problem and I dont think this should be supported in routerify itself since it can cause more problems then it solves. As I demonstrated above routerify doesnt really prevent you from doing this by yourself but this is an app specific issue rather than being a general issue in the domain what routerify tries to solve |
Beta Was this translation helpful? Give feedback.
-
@ta3pks, |
Beta Was this translation helpful? Give feedback.
-
Oh i see I got it wrong then. But in this case I dont think he should be involving routerify in his unit tests since he is not testing routerify but his own application logic. I still believe this is not a case routerify should try to solve this seems a design issue with the app that utilizes routerify |
Beta Was this translation helpful? Give feedback.
-
How do people do write unit tests against handler that use Routerify's request data?
Beta Was this translation helpful? Give feedback.
All reactions