Consider using different data attribute

[marcoroth]

Thanks for publishing this library!

I just wanted to bring to your attention that using the same data-action attribute is going to cause some "trouble" given that this is conflicting with the way Stimulus is declaring actions. Tools like Stimulus LSP aren't able to detect that this as a "valid" Stimulus Controller/action.

[eelcoj]

I've made sure it works with Stimulus (which attractive heavily takes inspiration from).

Since it is still 0.x version, exploring other options would be good. I personally like "readable" code. So something like this:

<button on="toggleClass#active" to="#content">
  Toggle
</button>

<p id="content">
  This element should toggle the `active` class.
</p>

Or maybe?

<button add-action="toggleClass#active" to-target="#content">
  Toggle
</button>

<p id="content">
  This element should toggle the `active` class.
</p>

More boring:

<button attr-action="toggleClass#active" attr-target="#content">
  Toggle
</button>

<p id="content">
  This element should toggle the `active` class.
</p>

Also boring but shorter:

<button a-action="toggleClass#active" a-target="#content">
  Toggle
</button>

<p id="content">
  This element should toggle the `active` class.
</p>

(where attr and a are abbreviations from attractive)