Eric Jolibois comments

Results 115 comments of


                                            Eric Jolibois

feat: add computed fields

Just resolved conflits. Please review whenever you can for the global approach🙏 There is still some debate on the API

feat: add computed fields

> As already mentioned by others, it would be great if we could control if such a field appears or not in the repr. @smarie `repr` has been added. Feedback...

JSON Schema Nullable Required Syntax?

Hi everyone **In the meantime here is a generic workaround**: ```python from pydantic import BaseModel as PydanticBaseModel class BaseModel(PydanticBaseModel): class Config: @staticmethod def schema_extra(schema, model): for prop, value in schema.get('properties',...

JSON Schema Nullable Required Syntax?

Hello @HacKanCuBa Which version of _pydantic_ do you use? Could you please provide a `gist` or something to help me understand

JSON Schema Nullable Required Syntax?

Hi @HacKanCuBa I just updated my answer with the generic version to add the case of `$ref` when we have a `BaseModel` in the schema. Please tell me if it...

JSON Schema Nullable Required Syntax?

@HacKanCuBa Glad you could test it and catch new errors! Thanks for that 👍 It means https://github.com/samuelcolvin/pydantic/pull/1611 will need some changes!

JSON Schema Nullable Required Syntax?

So basically we could have an enum option in the config like `extra`. IMO it makes no sense to put it at field level as you either want your schema...

JSON Schema Nullable Required Syntax?

You could just do ```py from pydantic import BaseConfig BaseConfig.schema_nullable = '...' ``` or define your own custom `BaseModel` since `Config` is inherited from parent classes

JSON Schema Nullable Required Syntax?

Hmm but that's not the same problem. My point was: you probably either want "nullable" to be set in the schema or not. But you don't want to set it...

Implement proper support for nested complex env values

I would also differ this for v2