Implement v-on and v-bind

[DavidBerger98]

v-on and v-bind were not mapped from python keys to vue keys, which made it not possible to implement and example like this:

with vuetify.VMenu():
    with vuetify.Template(v_slot_activator="{ on, attrs }"):
        with vuetify.VBtn(icon=True, v_bind="attrs", v_on="on", v_on_click="test"):
            vuetify.VIcon("mdi-dots-vertical")
    with vuetify.VList(), vuetify.VListItem(
        v_for="(item, i) in menu_items",
        key="i",
        value=["item"],
    ):
        vuetify.VBtn(
            "{{ item }}",
            click=(print_item, "[item]"),
        )

Note: The list of v_on_names does not cover all possibilities yet. Since you can chain most of the keywords in different ways, we should probably build the list programmatically. (e.g. v-on:click.self.stop.prevent etc.)

[DavidBerger98]

@jourdain While we're at the topic of self._attr_names, wouldn't it be more efficient to have them as a class variable rather than instance variable? Subclasses of AbstractElement could then add new attr_names with __init_subclass__ (https://peps.python.org/pep-0487/). It is only supported for Python>=3.6, however seeing that support for Python 3.5 has been dropped, we may make use of that method.

I can create an issue for that and start working on it, but thought I would ask you first. WDYT?

[jourdain]

I'm not sure I agree as not all HtmlElements are equals and they don't have the same set of available attributes. Moreover, if you have a unique list, you start having more chance of conflict between attributes and events.

Finally, for any advance usecase, you can provide the list of attributes/events to process for a given instance. So even if the default are missing something, you can still make it work.

[jourdain]

But I'm fine merging your current changes.

[DavidBerger98]

I'm not sure I agree as not all HtmlElements are equals and they don't have the same set of available attributes. Moreover, if you have a unique list, you start having more chance of conflict between attributes and events.

Finally, for any advance usecase, you can provide the list of attributes/events to process for a given instance. So even if the default are missing something, you can still make it work.

I see! I thought that _attr_names is a read-only list of available attributes for that type of HTML element.

But then nvm, thank you for the clarification!

[jourdain]

🎉 This PR is included in version 1.20.0 🎉

The release is available on:

• GitHub release
• v1.20.0

Your semantic-release bot 📦🚀