Thank you for your proposal.

However, it seems to me that the options you have proposed are a bit limited.

The following is my idea.

Add the ignorePatterns option. You can specify an array of regular expressions with the ignorePatterns option.
Ignores event names whose names match the specified pattern from this rule's report.

e.g. "ignorePatterns": ["^[a-z]+(?:-[a-z]+)*:[a-z]+(?:-[a-z]+)*$"]

What do you think? Does the ignorePatterns option solve your needs?

Yeah that works! Thank you @ota-meshi 🙏

Vuetify also uses : syntax for events, for example click:row, so that would be a great addition

👍 Vue itself uses examples of update:my-prop to distinguish which prop is being updated.

@bitencode custom-event-name-casing rule already ignores update:my-prop.
If update:my-prop is reported as an error in your environment, could you open a new issue?

My apologies @ota-meshi, it does ignore that specific use case. When I upgraded to the new version of this plugin we had hundreds of errors about "must be kebab-case" that I missed the fact that using update:<prop-name> events were not in the list of errors.
We took the original Vue examples as being a good way of specifying a resource or context and an action, so we update props with that syntax, and then for lower level components we emit events similar to Vuetify and use events like change:sort-order, change:per-page, etc... Higher level components use higher concept events to notify their parents of what they are doing - like video:start, video:stop, etc... so all those events are resulting in lint errors. For now I have just disabled the rule.
Thank you