Хусниддин
Хусниддин
When creating a new migration, I think this bug(error) only occurs with ForeignKeys, details below: ``` my_app/tables.py ``` ```python class Order(Table, tablename="orders"): user = ForeignKey( LazyTableReference( table_class_name="Users", module_path="users.tables" ) )...
I don't know if this is an issue with **jprq**, but I'm sure it can cause affliction, as it did for me. When I create a tunnel, Yandex/Google's Crawler Robots...
passed the `schema_extra` parameter to each method where `create_pydantic_model` is called in PiccoloCRUD
https://github.com/piccolo-orm/piccolo_api/blob/e2f8ce83a29234d0e6a79b4add044be71b904637/piccolo_api/crud/endpoints.py#L294-L304 Why is schema_extra not passed to the following methods as in this method above? ``` pydantic_model_output pydantic_model_optional pydantic_model_plural ``` When I use my pydantic basic config it only works...
- [ ] [aiogram-deta](https://github.com/aiogram/deta) ([patch](https://github.com/Mortasen/deta)) - [ ] fastapi for webhook and web app - [ ] update structure and other
By adding dynamic prompt editing (in the web app), we can get rid of error-generated suggestions by providing a unique/right prompt each time.
Implementation of all (from the Merchant API only [SetFiscalData](https://developer.help.paycom.uz/metody-merchant-api/setfiscaldata) left) methods from payme docs to get a **full-fledged** package. - [ ] add SetFiscalData method
- [x] More tests - [ ] Add to `py manage.py test` command - [x] Test on Pull Request (Github Actions)
**Add a detail object to Order model** Detail key | Type | Summary | Required -- | -- | -- | -- `receipt_type` | Number | Sale/Refund = 0 |...