+1 for Johannes, I can't see why would a little wider selection of severity levels hurt. The priorities Logbook uses are just fine, more can't be needed in web context, but only 4 is not very flexible.
As for the naming, I'd vote for the current implementation, because I don't think the change is really needed. It's widely used and I don't feel it really inconsistent compared to "$logger->addXY()" (but maybe we can consider "$logger->logXY()", not adding messages, logging them), and no BC break is possible with leaving it alone. But I believe this is more a Monolog matter than a Symfony one. > Interesting, I don't have notice on the docs I see [1]. > > [1]http://packages.python.org/Logbook/api/base.html#logbook.CRITICAL > I guess that's a documentation issue, because notice is present everywhere else I read. -- 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
