v1 changes

[vitalik]

Outlining here potential backward incompatible changes that might be introduced in v1 release

• auth will be class interface instead of callable (to support async authenticators)
• responses to support codes/headers/content (like general Response class)
• routers paths joined with "/" - which might not needed on some cases where router prefix will act like a prefix and not subfolder

[ahmadaidin]

is there any plan to add custom decorator support to the api module?

[vitalik]

is there any plan to add custom decorator support to the api module?

what do you mean ? example ?

[ahmadaidin]

is there any plan to add custom decorator support to the api module?

what do you mean ? example ?

I tried to implement an async decorator to check whether user exists or not on database before an API function is called. At first I got an error and I think it's impossible to add any async decorator for now. But then I found a way to create one and it works. So, I think it's already solved.

[mathiasag7]

When i add List[ModelSchema] in another schema, he generate an error "AttributeError: fields". I don't understand why

[WarKaa]

Hey @vitalik thank you for your great work

Will it be possible in v1 to add custom example to our open api schemas like in https://fastapi.tiangolo.com/tutorial/schema-extra-example/?h=example#pydantic-schema_extra ?

[rngallen]

When i add List[ModelSchema] in another schema, he generate an error "AttributeError: fields". I don't understand why

Kindly share your schema and models code. It will be easy to solve having some hints

[A-Asror]

will there be permission , for example, like django rest framework !?

and would like to be able to define serialization depth in schema class, example:

class UserSchemaIn(ModelSchema):

    class Config:
        model = UserModel
        depth = 1
        model_fields = ("password", "username", "email", "first_name", "last_name")