> I am using a yaml editor but the error was logical, not syntactical (I > left a field without a type). > A reference to the schema file causing the error and a line number > would be very helpful. Should I open a ticket for it? > There's another logical issue I've noticed and that's if I include the > same definition twice, as far as I remember the second definition is > used and no warning is shown. I believe a warning would be of great > help.
I'll concur on this point. I'm learning symfony and doctrine right now and would find warnings of unexpected yml attributes to be quite helpful, as I just spent 20 minutes trying to figure out why my custom routing wasn't working as expected (param, not params). Strictly parsing the configuration files would flatten the learning curve for new developers somewhat. - donald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
