thierrymichel/kapla

Tiny JS framework to manage DOM components

kapla's Issues

Add NoComponent

Custom events that not unbind

Hi (and thanks for Kapla!)

I've found these two problems related to events.
I've build a repo to test them and show you the code:
https://github.com/gfnool/kapla-test

1. If a component is listening to two custom 'global' events, when the component is destroyed only one of the event is unbind. This does not happen if the custom event type is 'component'
   https://kapla-test.netlify.app/global-events.html

2. If a dom node has two components attached and they are listening to the same custom event, when the node is destroyed only one of the listener is unbind.
   https://kapla-test.netlify.app/same-node.html

Are they known bugs?
Is there a better way to use global events?

Thank you!

Multiple "same-component" instances on the same "page"

I see the components are indexed in the Manager using their slug.
The slug is the name of the component "normalized" right?

I haven't tested, but we should check if we can have multiple "same components" on the same page, each one with its own instance.

Add more tests

Improve tests and coverage to avoid "testing-patching-publishing" workflow…

Web components?

I know, i'm late to the party 🎉 ...
Have you took in consideration to use web components instead of manually checking DOM mutation?

Web Components seems to have automatic lifecycle callbacks (connected/disconnected...) that may simplify the library meanwhile using a living standard. I'm sure there are also good polyfills methods for web components.

Add infos about component on errors

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

No longer Maintain ? Alternatives

Hello,

I've notice the end of the maintenance of the library.
Any suggestions for a replacement ?

Thanks !

init / destroy with subscribe / emit ?

Check it (val-dieu + hugues)

`app.components` should returns "real-time" initialized/loaded components…