allow object properties to be optional
|Priority:||Should have||Due date:|
|Target version:||Extbase 6.2|
When a model has validators the value may not be empty. To overcome this issue honour the @optional annotation for a property.
Note: instead of @optional the annotation could also be named @allowEmpty or @nullable.
Issues: The patch uses empty(), but this yields TRUE for "0" strings and 0 integers, which may or may not be expected. IMHO "0" is a problem, but 0 zero not in all cases (as TYPO3 doesn't allow NULL for integer columns anyway).
|related to Extbase MVC Framework - Feature #5973: EmailAddressValidator allow empty|valid email address||Closed||2010-01-12|
|related to Extbase MVC Framework - Bug #26617: DateTime validator should accept NULL dates||Closed||2011-05-04|
|duplicated by Extbase MVC Framework - Bug #9556: Validator: EmailAddress, Float, DateTime, ... not accept ...||Closed||2010-09-01|
Updated by Martin Kutschker almost 3 years ago
Just to clarify the case. This issue is not about optional controller arguments but about object properties that may be empty (or NULL).
Updated by Sebastian Kurfuerst over 2 years ago
- Tracker changed from Feature to Story
- Priority changed from Should have to Could have
This feature needs to be in sync with FLOW3.
Updated by Ingo Pfennigstorf 8 months ago
- Status changed from New to Accepted
- Priority changed from Could have to Should have
- Target version set to 6.1.0
- Has patch set to No
Good one, stumbled over this a few times in the past