You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bundle should come with an automatic development mode, such that when the Symfony environment is detected to be in Development mode the bundle reacts accordingly. This should include the in built reporting API, activating logging internally for services like fetch metadata, and including in some level a profiler within symfony's built in profiler service.
Actual Behavior
At present a services_dev.yaml file exists however it is not correctly wired into the container service. This can be used to register specific services such as the profile and report-to controller such that they are not made active in production mode where they might cause resource or information leaks.
Steps to implement a solution:
Wire up development services with the services_dev.yaml
Create a development configuration tree
Implement Symfony's internal logger in required services
Ensure that there are no "trailing" routes in production mode
Setup and configure a Symfony profiler for a more integrated development experience
The text was updated successfully, but these errors were encountered:
Expected Behavior
The Bundle should come with an automatic development mode, such that when the Symfony environment is detected to be in Development mode the bundle reacts accordingly. This should include the in built reporting API, activating logging internally for services like fetch metadata, and including in some level a profiler within symfony's built in profiler service.
Actual Behavior
At present a services_dev.yaml file exists however it is not correctly wired into the container service. This can be used to register specific services such as the profile and report-to controller such that they are not made active in production mode where they might cause resource or information leaks.
Steps to implement a solution:
The text was updated successfully, but these errors were encountered: