Feature #33058
Choice for XML Configuration
Status: | Rejected | Start date: | 2012-01-09 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Karsten Dambekalns | % Done: | 0% |
|
Category: | Configuration | |||
Target version: | - | |||
PHP Version: | Complexity: | easy | ||
Has patch: | No |
Description
Though YAML seems to be much simpler then XML, but companies whose staff is trained to use XML instead of YAML. It would be a nice idea to have Configuration parser which could either use XML or YAML based on developer choice.
History
#1 Updated by Karsten Dambekalns over 3 years ago
- Category set to Configuration
- Status changed from New to Rejected
- Assigned To set to Karsten Dambekalns
- PHP Version deleted (
5.3) - Complexity set to easy
Our approach to keeping things simple means: one configuration format is enough. Especially if not knowing YAML is the only reason to ask for this feature. In this case the added complexity doesn't seem to be worth it.
But: feel free to come up with an XmlSource
class implementing \TYPO3\FLOW3\Configuration\Source\SourceInterface
- if you really need it.