Input Element As Custom Component

[sid]

Hi.
We are doing a quick test on how custom components work.
We want to create a custom input-type based component, similar to the autocomplete component provided by Wappler.

When setting the TEMPLATE property in HJSON as <input is="dmx-custom..." ....>, the properties in the properties panel do not show. Instead, regular input text properties are shown.
Autocomplete component has a similar temlpate, but it works fine.
When setting template as <dmx-custom>...</dmx-custom>, the properties show up correctly.
What are we doing incorrectly? Or is it a bug?

Also, would you guys be interested in sharing some existing component’s HJSON and un-minified JS code as real-Wappler examples on building custom components?

[sid]

Bump.

[JonL]

You can use the priority option.

Wappler Extensibility - Build Custom App Connect Extensions

The next level of Wappler extensibility - App Connect for our front-end framework is here! Building custom App Connect custom components with their own dynamic attributes, events and data sources is now possible. You can write your own custom components and also provide a UI definition of your extensions so they integrate directly visually in Wappler! Your extensions can be published on Github and NPM, so they can be easily installed in Wappler as versioned packages and also use their own de…