Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Requirements:
- Some config entites don't have full validation yet
- Some config entities might not want to be exposed at all?
Coming from #2300677: JSON:API POST/PATCH support for fully validatable config entities
Comments
Comment #2
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedI think it would almost be more sensible to discuss "what are the bare minimum requirements a config entity has to implement for REST support to even be an option". We can come up with a way to opt out, but unless we have a way of evaluating if a config entity is "rest ready", then it's a tricky discussion/evaluation to have for each one. I think answering this will largely come down to how some of the key technical challenges are going to be tackled, which looks like it's being discussed in the parent issue.
Comment #3
dawehnerFor me these points would be helpful:
a) All form validation got checked and ensured it got moved to constraints
b) All form element based validation (a select list ...) got checked and got moved to constraints
c) We have a basic kernel test which tests validation on typed data level ...
Comment #5
gabesulliceI'd like to propose #2936714: Entity type definitions cannot be set as 'internal' as the mechanism for config entities to do this. Leaving this issue for discussion about "what are the bare minimum requirements a config entity has to implement for REST support to even be an option"
Comment #6
Wim Leers#5++
Comment #7
dawehnerI'm totally happy with the solution outlined by @gabesullice in #5
Should we mark it as RTBC and be done with it?
Comment #8
Gábor HojtsyIn that case, this would be a duplicate of #2936714: Entity type definitions cannot be set as 'internal'? In terms of code/docs (policy) update that is.