Ad Approach 4: Prefixing or suffixing services still leaves one problem unattended: What if DI variables (like $maxPerPage) collide with request parameters? Naming it $maxPerPageService obviously makes no sense.
Also, having a different magic in the constructor ($mailer) and the actions ($mailerService) could be confusing for many developers. My personal feeling is that the magic in the action methods may lead to problems in big projects with lots of DI configuration. There it can easily happen that services or DI variables collide with request parameters. Unfortunately these collisions may not be obvious. So, if we take this approach (which is compatible to most other approaches) Symfony should warn the user when such collisions occur. Bernhard -- 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 To unsubscribe from this group, send email to symfony-devs+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
