Josh Yu
                                            Josh Yu
                                        
                                    浏览了一些 `SQLAlchemy` 的 issues,大部分网友认为这个报错可能不是 SQLAlchemy 引起的。 你可以尝试检查一下外链的依赖问题,比如 User 如果也使用了 `Basemixin`,当定义 `db.ForeignKey("t_user.id")` 的时候,是不是依赖了一个并不存在的表。
我也用的 375 设计稿,是有什么问题吗? @jiwenjiang
@scclsy 你的设计稿是多少宽度? 官方文档对这块有说明的。 ``` 结合过往的开发经验,Taro 默认以 750px 作为换算尺寸标准, 如果设计稿不是以 750px 为标准,则需要在项目配置 config/index.js 中进行设置, 例如设计稿尺寸是 640px,则需要修改项目配置 config/index.js 中的 designWidth 配置为 640: ``` https://taro-docs.jd.com/docs/size#%E9%85%8D%E7%BD%AE
I really need this feature.
Maybe you can take a look at hooks https://docs.ponyorm.org/api_reference.html#entity-hooks
Probably the same issue as this: https://github.com/ponyorm/pony/issues/104
@sydney-runkle Any news on it?
@sydney-runkle I found v2 try to split Annotated field to `type` and `metadata`. for example: ```python q: Annotated[list[str], Query()] ``` It will be split to 2 parts in FieldInfo instance:...
@sydney-runkle The is another issue that, metadata `Query()` will lost in classmethod `FieldInfo.from_annotation` ```shell >>> annotation typing.Annotated[list[str], Query(None)] >>> result = FieldInfo.from_annotation(annotation) ``` `result.metadata` is empty list. It should be...
@sydney-runkle After more research, I found the v2's annotation is different design of v1's, some information is stored in metadata attribute in v2. My case is work with FastAPI, A...