props casing best practices - camelCase in templates ok?

[theoephraim]

The official vue style guide suggests defining props using camelCase and then using them in components with kebab-case. While I have certainly gotten used to it, I am questioning whether it still truly makes sense...

I understand the reasoning to be:

1. compatibility for those using DOM templates because HTML is case insensitive
2. consistency with built in HTML attributes / the context they are being used

On the flip side, keeping the name consistent has huge benefits when thinking about project-wide search, find/replace, and refactoring tools.

I'd also think that the DOM template issue does not apply to a huge number of vue users (especially power users), and that a counterpoint can easily be made for distinguishing between html attributes versus props - similar to the reasoning behind the suggestion to use PascalCase for component names.

Is there any appetite out there in the community to relax this recommendation and say it's acceptable to start using camelCase props in templates - with the caveat about DOM templates - very similar to what we have now with component naming.

[theoephraim]

hooray! Thank you @NataliaTepluhina

https://github.com/vuejs/docs/pull/2161/files