Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DependencyInjection] Add the possibility to disable assets via xml#24706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
df5822e to0b9258dCompare
chalasr left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Should be merged on 3.3, the lowest maintained branch where the assets configuration can be enabled in other formats.
renatomefi commentedOct 27, 2017
@chalasr thanks, will do it shortly |
0b9258d to24d9375Compare24d9375 to44588faCompare44588fa to8579e24Comparerenatomefi commentedOct 27, 2017
@chalasr all done! :) |
nicolas-grekas commentedOct 28, 2017
Thank you@renatomefi. |
…s via xml (renatomefi)This PR was merged into the 3.3 branch.Discussion----------[DependencyInjection] Add the possibility to disable assets via xml| Q | A| ------------- | ---| Branch? | 3.3| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | no| License | MIT| Doc PR | no- When trying to disable the assets using xml configuration I realized it wasn't possible, this patch fixes and tests it- Also added extra tests since the assets being disabled was being tested on both php and yaml Extension testsCommits-------8579e24 [FrameworkBundle] Allow to disable assets via framework:assets xml configuration
chalasr commentedOct 28, 2017
@renatomefi Congrats for your first contrib on Symfony! Nice PR, well done. |
renatomefi commentedOct 29, 2017
Thank you@chalasr :) |
Uh oh!
There was an error while loading.Please reload this page.