Jason Desrosiers
Jason Desrosiers
The same error exists on line 256. That should be fixed as well.
The only time I want to use type conversion is when I am validating $_GET input because there is no way for a user to explicitly declare their types. However,...
I'm not actively doing PHP development at the moment either. So, don't go out of your way just for me.
I agree that there's probably a missing `createOnly` annotation. Forbidding the field like in @karenetheridge's suggestion isn't going to be sufficient for PUT requests which should be the full representation....
> > you can't leave the read-only field out, you need to provide it unchanged. > > This seems weird. If field is read-only then it means PUT request can't...
If the schema is wrong, it's my fault. Reading the spec it doesn't appear that one of "url" or "identifier" is required, but I'd be surprised if that wasn't the...
Understood. Unless @arno-di-loreto already has something prepared, I'll update the schema.
I'm impressed that you found nearly every possible way to express this constraint. The only one I'd actively discourage is Option 1. It could be reworked to reduce the duplication,...
I'm not sure this solves your problem, but checkout the [third example](https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.section.8.6) from a section of the 2020-12 JSON Schema, which is supported in OpenAPI 3.1.
Can you be more specific? What would `propertyType` look like? What problem are you trying to solve?