-
Notifications
You must be signed in to change notification settings - Fork 424
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
Kebab-cased or underscore_cased targets #70
Comments
I'd be more than happy to have a crack at a pull request for adding the automatic conversion from camelCase to kebab-case if it's something you'd be open to considering. |
Yep! We plan on documenting this in more detail after 1.0, but here’s a rundown of the capitalization conventions, with a bit of rationale for each:
|
Awesome, thanks for that - good to know. Sorry about all the beta related questions, was hoping to help out where possible. |
If you have a multi-word target name it seems like the convention would be to kebab-case or underscore_case it's name as opposed to camelCase because of the way the controllers are named. However, this doesn't pair nice with the new class
targets
coming in1.0.0
.For example, if I have a target called
document-input
I wouldn't be able to use a friendly getter as a method, I'd have to call it through it's key instead.Would the convention be to stick to camelCased target names so it can all look nice in the controllers, or could the class targets be converted from camelCase to kebab-case under the hood so that we can use the former in our scripts and the latter in our views?
The text was updated successfully, but these errors were encountered: