Refactor useMutationObserver hook to manage subtree modifications

[CarlosCortizasCT]

Summary

Refactor useMutationObserver hook to manage subtree modifications.

Description

If we currently pass the subtree option to the useMutationObserver hook, we're not going to have our mutation callback called. This is because we can have a same MutationObserver observing different elements and, when we get the internal mutation callback in our hook, we check to see wether the mutated element is one of the ones we have previously registered.
In the case of adding a direct children to the observed element, that's not a problem; however, if we add a grandchildren to the observer element, consumers won't know about it because the mutated element will be an observer element child and we didn't registered those in our hook.

With this change, we introduce some changes for consumers to be allowed to be notified about nested elements mutated within the one registered in the hook.

In this first attempt, a selector is needed by the hook to check whether a mutated element is contained in the observed element.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ui-kit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 21, 2024 4:43pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: a930c3d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CarlosCortizasCT]

Closing as this PoC was abandoned.