@marblejs/middleware-logger extend filter options about marble

[JozefFlakus]

@knopki Hah, you are right. I was confused by the API which I authored 🤦‍♂️.

@SORC3r3r I'll add also support for filtering incoming requests in the upcoming v2.1 release.

I think that the end API will look like this:

logger$({
  filter: (res, req) => ... // you can validate only `req`, only `res` or both
}),

So the signature will look like this:

(res: HttpResponse, req: HttpRequest) => boolean;

[JozefFlakus]

Version 2.1.0 has just been released. As described above, you will be able to filter not only by response but also by request. If there will be something missing I'll reopen this issue.

Thanks! 💪

[JozefFlakus]

Yup, you can do this easily.

import { logger$ } from '@marblejs/middleware-logger';

const middlewares = [
  logger$({
    filter: req => ... // filter out specific `req.url` paths
  }),
  ...
];

export default httpListener({ middlewares, effects: [] });

https://docs.marblejs.com/api-reference-2/middleware-logger#usage

[knopki]

@JozefFlakus just to clarify, logger$'s filter's signature is (res: HttpResponse) => boolean; and HttpResponse doesn't have url property.

[SORC3r3r]

Awesome, works perfectly fine! 👍