-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Improvement] Use consistent CamelCase filenames derived from BE/CE type names #46
Comments
@Moongazer nice! we should think about fallback on the frontend, so components with underscore should be registered as depracated for some time. What do you think ? |
OK I implemented the CamelCase naming for content-elements, including a fallback for the old naming. But for the BE page types it might work a bit different, I've to checkout that out first. |
mercs600
pushed a commit
that referenced
this issue
Jul 9, 2020
mercs600
pushed a commit
that referenced
this issue
Jul 9, 2020
mercs600
pushed a commit
that referenced
this issue
Oct 29, 2021
mercs600
pushed a commit
that referenced
this issue
Oct 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name parts for BE page and CE types in TYPO3 can only be seperated by underscores, which currently results in non consisting filenames like CeMenu_pages.vue (proper CamelCase like CeMenuPages.vue would be better)
The text was updated successfully, but these errors were encountered: