Outlets array expects kebab-cased names instead of camel-cased ones (like targets do)

If you have a target name which consists of multiple words, you’ll define your targets as follows:

static targets = [ "errorMessage" ]

An outlet name with multiple words, has to be defined the following way:

static outlets = [ "error-message" ]

If this is the intended behaviour, it would be nice to add a small notice to the documentation. Thanks!

[NakajimaTakuya]

I generally agree with the alignment with the targets api. However, I have one concern. If outlets are written in CamelCase, there is no way to distinguish between -- and -.

before:

// in html
data-controller="hoge"
data-hoge-xxx-yyy-outlet="#zzz"
data-hoge-xxx--yyy-outlet="#ppp"

// in controller
static outlets = ['xxx-yyy', 'xxx--yyy']

after

// in html
data-controller="hoge"
data-hoge-xxx-yyy-outlet="#zzz"
data-hoge-xxx--yyy-outlet="#ppp"

// in controller
static outlets = ['xxxYyy', 'xxxYyy'] // I do not know which of these refers to which.

Originally, outlet getter had this problem. However, it used to be discernible at the time of definition and it was predictable that the two would be mixed.

Wouldn’t it be difficult to work backwards from the outlets static property to the controller name, given the existence of -- and - in the first place?

[dhh]

Would be happy to ship a quick 3.2.2 that addresses this. If there was a way to detect kebab case, still have it work with a warning of depreciation, and then document and recommend camel going forward, that would be great.