You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using express 5 job results can no longer be seen:
I've tracked this down to a breaking change in express 5 where req.query has become a getter, whereas in express 4 it was set as part of a middleware function:
This leads to req.query being undefined in libraries that pull in express 4 (like bull-board). For bull-board this causes no active queue to be selected, and so no jobs for that queue are returned. I think this could be fixed if we were to set the express dependency to >=4.17.3.
In the meantime, this can be used as a somewhat hacky workaround:
router.use("/queues",(req: Request,res: Response,next: NextFunction)=>{constquery=req.query;// Set query as a property on req instead of as a getter for backwards// compatibility with express 4Object.defineProperty(req,"query",{get: ()=>query});next();},serverAdapter.getRouter());
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When using express 5 job results can no longer be seen:
I've tracked this down to a breaking change in express 5 where
req.query
has become a getter, whereas in express 4 it was set as part of a middleware function:This leads to
req.query
being undefined in libraries that pull in express 4 (like bull-board). For bull-board this causes no active queue to be selected, and so no jobs for that queue are returned. I think this could be fixed if we were to set the express dependency to>=4.17.3
.In the meantime, this can be used as a somewhat hacky workaround:
The text was updated successfully, but these errors were encountered: