POC Monkey-patch history pushState and replaceState to listen to location changes

[zanderle]

Closes #157

[zanderle]

@humitos this just does the monkey-patching for now (haven't added any listeners yet). Do we want to do a test-build with this, to see if it correctly picks up the "page changes", before we move on to the next step?

[humitos]

I did a small review and left a few questions.

[humitos]

Do we want to do a test-build with this, to see if it correctly picks up the "page changes", before we move on to the next step?

How hard would it be to create a simple example for this using the index.html page from this repository?

I tested using test-builds locally and I can confirm the custom method is called when changing pages on Docusaurus and Material for MkDocs (I added some small console.log) --but I don't want you to deal with my current setup since it's a complex.

[zanderle]

Do we want to do a test-build with this, to see if it correctly picks up the "page changes", before we move on to the next step?

How hard would it be to create a simple example for this using the index.html page from this repository?

I tested using test-builds locally and I can confirm the custom method is called when changing pages on Docusaurus and Material for MkDocs (I added some small console.log) --but I don't want you to deal with my current setup since it's a complex.

I think I can make it work locally, to develop, and then I'll ask you to do a proper test on your setup

[agjohnson]

Changes here seem fine, no additions to the notes here 👍

[zanderle]

Do we want to do a test-build with this, to see if it correctly picks up the "page changes", before we move on to the next step?

How hard would it be to create a simple example for this using the index.html page from this repository?

I tested using test-builds locally and I can confirm the custom method is called when changing pages on Docusaurus and Material for MkDocs (I added some small console.log) --but I don't want you to deal with my current setup since it's a complex.

I added this to the PR, but we can remove it, if you think it's redundant

[humitos]

Looks good.

This is the first step required for the underlying work. Here, we are detecting that the URL has changed and triggering a custom event, which is 💯

The next step here is to subscribe and use this event to reload all the addons that require reloading. My idea is to investigate the usage of Lit context and make the config object to become an object shared by that context.

With that, we can subscribe to this event, re-fetch the updated data from the endpoint and update the config object so the addons refresh automatically.

I wasn't able to jump into exploring this idea yet, but I should probably do it soon.

[humitos]

Same here.

[humitos]

I pushed a few changes. I'm going to merge this work now so I can continue working on #491 and #504.