Serge Matveenko
Serge Matveenko
Does `validation_alias` implies `serialization_alias` to be the same? If it does than this is the solution we already support.
@BTripp1986 Could you please clarify, do you need `validation_alias` and `serialization_alias` both set for your use case?
@samuelcolvin Despite OP's case I really see how this is logical to have such an option. Additionally, using `alt_alias` should raise and error if `allow_population_by_field_name` is not enabled or even...
@sbasan I think it's worth mentioning that there is also `BaseModel.model_construct` which bypasses validation. While `BaseModel.__init__` and `BaseModel.model_validate` are indeed slightly different interfaces to validation (aka deserialization) the `BaseModel.model_construct` bypasses...
Only some points from this issue are good for a first issue. I suggest working on those things separately creating new issues and referencing those here.
cc: @dmontagu @samuelcolvin
Same here on two different vscode configurations on different laptops. How can I get those logs? I've already configured Ruff extension to use bundled Ruff as was mentioned in another...
I've recreated venv and now it works. Have no idea what that was 🤷♂
I'll try to debug this on a second laptop. Yes, I always have ruff installed via `uv tool` or `pipx` and another one in the project's venv.
@Keonik1 Also, supporting Traefik opens up k3s as a supported platform which looks like a great choice (and a popular one) for hosting a small project and self-hosting in general.