-
-
Notifications
You must be signed in to change notification settings - Fork 195
[Question] Where should the old app/Resources/ contents live now? #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
For now, it works if you put |
@javiereguiluz Sorry for picking up on a closed Question but could you share where |
@yakobe Try |
Just saying: I would expect this to live in (and if I want to overwrite a translation file: |
Yep, maybe the TwigBundle's extension can be updated to be able to change
Overriding translations is possible by adding a file in the For assets, it's more an Encore problem, and I'm not sure that it would be easily solvable... |
At risk of reopening old discussions: following #56, it seems Flex is moving towards a skeleton style structure with renaming web->public and etc->config. Skeleton also suggests making a |
@fabpot Thanks, that works 👍 I also agree with @javiereguiluz 's expectation that they would be in |
Of course... and we thought about that as well... see symfony/symfony#23339 |
This PR was merged into the master branch. Discussion ---------- Add a note about the contrib repo Commits ------- 7a172be added a note about the contrib repo
I'm switching the Symfony Demo app to Symfony Flex. I don't know what's the new practice to store the old
app/Resources/*
contents.For example,
app/Resources/views/
are nowtemplates/
but what about:app/Resources/translations/
->translations/
?app/Resources/TwigBundle/views/Exception/
-> ??app/Resources/assets/
->assets/
?The text was updated successfully, but these errors were encountered: