On 9/29/10 8:52 AM, Lukas Kahwe Smith wrote:
On 28.09.2010, at 22:00, Andrej Pavlovic wrote:
I am also worried about adding new custom options to XML
configurations. Wouldn't that break the XSD validator? How could that
be easily extended?
Depends on how you define the initial XSD. But yes in order to get validation
for new options you add in your bundle, you obviously need to add those to the
XSD.
No, validation is done on a per extension basis (validation for
app.config uses a different XSD than validation for doctrine.config).
Adding "options" is straightforward (just declare a parameter). Adding a
semantic configuration is done exactly in the same way for YAML or XML;
with the possibility to have an XSD for XML (but that's optional).
Fabien
@Fabien: Not sure about this, but I assume the validation is done on the final
XML after all parameter replacements are done?
regards,
Lukas Kahwe Smith
[email protected]
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
