-
-
Couldn't load subscription status.
- Fork 142
twig files in subfolder #19
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
Conversation
| So both |
| Si 👍 for this! |
| no only |
| Ok, but the current behavior is to autocomplete names like |
| sry too fast :) the common way would be: "Symfony2 uses a bundle:controller:template string syntax for templates. This allows for several different types of templates, each which lives in a specific location" futhermore |
| We shouldn't implement both for autocompletion, because we'd get 2x results. So I'd keep template autocompletion the same, but I'd allow "click to go to definition" on template name like What do you think ? |
| we should not provide double results on autocomplete, thats a good point. the solution to spilt this looks good to me. but which one use as default for autocomplete? a symfony2 parent bundle can overwrite other bundle template files. i correctly dont now if that feature can also reslove |
| I know! We can put a settings to choose whether the user want to use |
Symfony abstracts template path with a TemplateReference object, that is relative to a bundle, so this shouldn't change anything |
| And |
| i will later on check the behavior of other IDEs on this |
| I did a very little research on this issue. And all I was able to find was xxx:xxx/xxx:xxx.xxx.twig. I know it's not enough to jump into conclusions, but still some factors to consider while deciding. |
| its not about which one is better, its on developer which one he decide to use, its a bit problem when plugin supports only xxx:xxx/xxx:xxx.twig and your whole project is using xxx:xxx:xxx/xxx.twig and so when you don't want to mix syntax you'll be forced to rewrite it on x places which is not helpin' us ... so it should be configured btw i've never seen using of xxx:xxx/xxx:xxx.twig until now |
| @Haehnchen FYI, you pushed b201275 to the branch of this pull request |
| Hello, can I help this feature with anything? If so, please let me know :) |
| Well there are two cases:
It is the way I write template paths. :) |
its allowed to put twig files in subfolder this should fix the path resolver like mention in #17
AppBundle:Conversation/list:tableRowPart.html.twig
Folder/Subfolder/file.html.twig -> BundleName:Folder/Subfolder:file.html.twig