Thiemo Kreuz 7a32cba3ef Split validation and normalization into separate services ... This makes it possible to use these steps independent from each other. For example, a future patch can get rid of the re-validation that's done over and over again when the API is called. A significant change is that this gets rid of an expensive deep clone. It was necessary before exactly because validation and normalization was intertwined. Normalized properties would mess with the later inheritance. Strictly splitting validation and normalization (and executing them in this order) solved this. The only downside of this is that inherited properties are validated twice. But this is much less of a problem, compared to the deep clone, I would like to argue. This was always covered by tests. You can still see the tests fail when you flip the execution order of inheritance and parameter validation. Bug: T301337 Change-Id: Ie5728094f9ed813f53b709d8b5283c4b99dc7d63		2023-03-06 13:05:51 +00:00
..
Api	Use EventLogging::submit() to submit analytics events	2023-01-30 18:20:16 +00:00
Hooks.php	Use EventLogging::submit() to submit analytics events	2023-01-30 18:20:16 +00:00
TemplateDataBlob.php	Split validation and normalization into separate services	2023-03-06 13:05:51 +00:00
TemplateDataCompressedBlob.php	Fix use of formatnum in templatedata-invalid-length	2022-01-31 09:34:57 +02:00
TemplateDataHtmlFormatter.php	Add an "Edit template data" button to the TemplateData output	2022-11-08 13:36:38 +00:00
TemplateDataMessageLocalizer.php	Improve test coverage for HTML formatter code	2022-02-03 12:45:27 +01:00
TemplateDataNormalizer.php	Split validation and normalization into separate services	2023-03-06 13:05:51 +00:00
TemplateDataValidator.php	Split validation and normalization into separate services	2023-03-06 13:05:51 +00:00