Decision to use camelCase vs kebab-case for tags?

[h34lthbybr33]

May I ask the decision to use camel case vs kebab case when it comes to tags? Seems odd to have a blog-post-slug not match a blogPostTag?

Any thoughts from others on this?

[avitorio]

Hey,

It's been a while but I believe this was done because tags are stored in the schema.json, together with the custom fields. And camel case is the convention for keys in json. So all fields are camel case, and that was extended to tags.

[h34lthbybr33]

I get the json notation, but they're stored as `{"label":"Two Words","value":"twoWords"}` so I get it but I don't. You could change to kebab and wouldn't functionally change things, that I can tell?

…

On Wed, Oct 16, 2024, 10:17 PM Andre Vitorio ***@***.***> wrote: Hey, It's been a while but I believe this was done because tags are stored in the schema.json, together with the custom fields. And camel case is the convention for keys in json. So all fields are camel case, and that was extended to tags. — Reply to this email directly, view it on GitHub <#252 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLCUXFINZALTYEOBL6VWHWDZ34M5LAVCNFSM6AAAAABQCNHO7WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJWGYYDMMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[avitorio]

You're correct. We could use kebab case there, but making the switch now would probably break sites that use the current convention.

I am not against changing it, if there's community support behind the idea, but it would have to be done on a major version release with additional docs added for the breaking changes.