We had a case were a shared.write instead of a proper shared.owner was parsed by pydantyic, and has not thrown an error that write is not supported. Ofc it had no effect and caused a lengthy investigation, about unexpected access-control issues in our solution
tasks;
- [ ] add test-cases with wrong configs
- [ ] improve pydantic parsing, and enforce errors
We had a case were a
shared.writeinstead of a propershared.ownerwas parsed by pydantyic, and has not thrown an error thatwriteis not supported. Ofc it had no effect and caused a lengthy investigation, about unexpected access-control issues in our solutiontasks;