Production Ready fastapi-radar

[doganarif]

We need to make FastAPI-Radar production-ready. should consider code coverage and performance impacts.

[NostraDavid]

coverage

There is basically coverage.py (it's an old name) (run coverage run --module pytest), and pytest-cov, which basically connects pytest and coverage so you would only need to run pytest --cov (IIRC - do check the docs).

You'll have to dig into settings for each - I would start with just coverage; I don't recall exactly what, but pytest-cov gave me some compatibility issues about a year ago. Maybe that has improved though.

[doganarif]

Yes, but FastAPI-Radar primarily binds itself to the FastAPI instance, so we need to calculate/consider its effects on the request lifecycle.

[NostraDavid]

Check out my pyproject.toml for configuraiton (the repo has a weird licence due to me making a fork, but I don't think anybody is going to sue you for some pyproject.toml configuration - use at your own discretion, I guess.)

[doganarif]

Thanks! @NostraDavid

[NostraDavid]

Looks like FastAPI itself also uses a coverage config

[qinsehm1128]

是的，但是 FastAPI-Radar 主要将自身绑定到 FastAPI 实例，因此我们需要计算/考虑它对请求生命周期的影响。

This is exactly what I'm worried about. I want to add asynchronous listening and httpx External request monitoring, but I'm worried that it might affect the corresponding cycle of fastapi, and due to context limitations, it might lead to data being read by middleware. This has been a problem I've been troubled by. However, I know that OpenTelemetry also uses the Monkey patch to mount sqlalchemy. I think my idea is that it can be tested Tested and verified

[doganarif]

#39