Support attribute sourcing about block-interactivity-experiments

[ockham]

I gave this a stab: #30

(I overall agree with your reasoning @michalczaplinski, but since @luisherranz had laid out the problem so nicely in his video, it felt like a "good first issue" for me to finally play with this repo 😄 )

[michalczaplinski]

I think the initial “work” could be just to evaluate if it’s worth the effort at this point before diving into implementing it.

As @luisherranz mentions in the video, the attribute sourcing was originally created so that the attributes do not get out of sync with the content saved in the DB. But our main use case is to reduce the duplication of content aka reduce the size of the payload.

So, for example, if there exists another way to deduplicate the content, it would probably negate the need for attribute sourcing altogether.

[ockham]

I think we can close this, now that #30 has been merged 🙂

[luisherranz]

Now that we've moved the wp-block wrapper to PHP, this has started to make sense 🙂