dni ⚡
dni ⚡
i propose we move mempool integration into core.services, i see multiple extensions already using it and i also need it in boltz extension. i think it is not a very...
WIP: boltz v2, adding recurring reverse swaps and clean code - add status to statusdialog - first commits for boltz update
- explicitly exclude all extensions from mypy - fix example extension mypy - fix subdomains extension mypy + 1 type error fixed - fix mypy discordbot - fix mypy copilot
my progress currently is about 1 block every ~3-5 minutes a this rate i probably will never finish, not sure what is wrong. i also notice when i start indexing...
this logically groups api endpoints and gives them specific openapi tags. which makes them nice on the `/docs` endpoint and makes the `api.py` more approachable
boolean if route hints for private channels will be included from `LndRest` inside bolt11 invoice. note: fundingsources do not have more than text inputs yet when rendered
recommended use: https://fastapi.tiangolo.com/advanced/events/?h=lifespan threw warnings in pytest ``` tests/core/test_db.py::test_create_wallet_and_delete_wallet /home/dni/repos/lnbits/lnbits/lnbits/app.py:467: DeprecationWarning: on_event is deprecated, use lifespan event handlers instead. Read more about it in the [FastAPI docs for Lifespan Events](https://fastapi.tiangolo.com/advanced/events/)....
this is especially useful for extensions. with this an extension can only call `create_permanent_unique_task("my-ext", task)` and it will restarted when it exists and cancels when lnbits is stopped