Draft: Support oxlint-compliant version of the plugin

[fsubal]

oxc-project/oxc#9905 (comment)

oxlint is going to support custom plugin APIs, similar but slightly diffrent from the one for eslint (maybe?).

What if we create oxlint version of eslint-plugin-classnames ?

[overlookmotel]

Oxc team member here. I had a quick look at this plugin and, while it won't work out of the box with very first version of Oxlint JS plugins, it should do as soon as we support messageId in reports - that looks to be the only API you're using that we won't have in 1st version. Hopefully won't take us too long to get to adding it. So if you can wait a little, you shouldn't need to make any changes, and your plugin should work with Oxlint same as it does with ESLint.

Thanks for your enthusiasm! 😄

[fsubal]

Thank you for your comment!

it should do as soon as we support messageId in reports - that looks to be the only API you're using that we won't have in 1st version.

I'm glad to hear this. It convinced me that it's not essentially so hard to support your plugin system.

While I'm not sure I have a time when the 1st version is released, but I'm looking forward to make a try 👍 .