a5r0n

> We need better documentation regarding the RequestCtx implementing the Context interface. The channel returned by `RequestCtx.Done()` is only closed [when the server is shutting down](https://github.com/valyala/fasthttp/blob/c94581c0055174e7588b2473dcd3b8a7612500d0/server.go#L2691). And for performance reasons...

in my tests, the nested object saved in collection as `header_id`, not `headerId`, so the expression is `{'header.header_id': 1}`

if u save this items with beania, it's saved with `header_id`, so we can't change the expression behavior.. am i right?

sorry 🙊 u are right. but i think we should save it by name (as pydantic default), or at least make it configurable?

i think we should separate all mongo related operations to one one function, as is need to be async. and all the Model initialization things to sync function. this way,...

Of course, I therefore proposed to divide the operations into two separate functions. For example, unit tests for queries, there no need any interaction with mongo. Besides, not every time...

@Delgan Can you accept PR for this? I thought about adding `backtrace` parameter to `logger.catch()` and check it to set `backtrace_` to `None` in `Catcher`

@appleboy @thinkerou i'd love to hear your opinion

maybe it's better to Add new method as is a breaking change? @tulir what do u think?

I think it's better to add 2 new methods, `match_all` & `macth_any` It is more clear what the function does. then adding `all=True` param to already exists `match` function