Task #88233
open
Change order of fields in date range validator
0%
Description
If a validator has options, the custom error message is always the last field. The date range validator is an exception and should be streamlined.
Updated by Björn Jacob over 5 years ago
- Status changed from In Progress to On Hold
- Assignee deleted (
Björn Jacob) - Sprint Focus deleted (
Remote Sprint)
This is kind of breaking since we have to change the key. People with customized configs could be in trouble (unset, already in use). We are waiting with this change and fix it together with other breaking changes.
- File: \TYPO3.CMS\typo3\sysext\form\Configuration\Yaml\FormEditorSetup.yaml
- line 659, identifier: 'minimum' key 250 -> should be less than 200
- line 669, identifier: 'maximum' key 300 -> should be less than 200
Updated by Björn Jacob almost 5 years ago
- Target version set to Candidate for Major Version
- TYPO3 Version changed from 9 to 10
Updated by Björn Jacob over 2 years ago
- Status changed from On Hold to In Progress
- TYPO3 Version changed from 11 to 12
- Sprint Focus set to Remote Sprint
12.0 is in development and therefore breaking changes are allowed. On it finally :)
Updated by Gerrit Code Review over 2 years ago
- Status changed from In Progress to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/73684
Updated by Björn Jacob over 2 years ago
- Status changed from Under Review to On Hold
- Sprint Focus deleted (
Remote Sprint)
We decided to deprecate the order in v12 and will breake (i.e. remove) it in v13. Therefore, this issue has to wait till the development of v13 starts.
Updated by Riccardo De Contardi 7 months ago
- Related to Task #97019: Deprecate order of validation message added
Updated by Garvin Hicking 5 months ago
- Status changed from On Hold to Needs Feedback
Hi!
It's been some time, v13 dev is nearly close to being wrapped - is this issue still planed to be worked on, what should we do about the 'on hold' status? Thanks!