-
Notifications
You must be signed in to change notification settings - Fork 130
assetic generation path #40
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm not sure it's related, but despite I don't use assetic ( |
Nice, when do you think you'll merge it into master ? |
Hi @bonswouar i probably wait week or two, actually i need more feedback. |
Okay @helios-ag , I'll use this branch next week and let you know if I notice any problem. |
Okay, that works, though :
Also, I have a problem with the form field (didn't notice that new feature, it's not related to the branch I think). |
Hi @bonswouar, thank you for feedback, |
5'th version of the bundle support components. |
it would be cool if the path where assetic is to generate the js and stylesheet would be optional. or maybe simply offer an option if the js and stylesheet should be included at all, so that i can also add them to my own asset list and combine with the other assets and set that option to false.
/cc @chrootlogin
The text was updated successfully, but these errors were encountered: