Process loaded code when expanding diff views

[xPaw]

Link: https://github.com/thelounge/thelounge/pull/1839/files#diff-cf27c1d543e886c89cd9ac8b8aeaf05b

Hopefully the GIF explains what I mean:

[josephfrazier]

This sounds related to #416, since they both concern page changes that don't trigger reprocessing.

[xPaw]

I'm not sure that's entirely related, as your linked issue concerns navigation (pjax), while this changes the page state without navigation.

[stefanbuck]

I agree with @xPaw. This issue is slightly different. It should be relative easy to fix.

We're happy to provide mentor help for people who want to pick this up.

[leomoty]

Hey @stefanbuck, any pointers for this one?

[stefanbuck]

At its core, it's just about calling run which will basically re-invoke the whole extension.

OctoLinker/packages/core/octo-linker.js

Line 20 in e218001

async function run(self) {

[leomoty]

@stefanbuck I have a preliminary version working with MutationObserver, I am looking for addedNodes that contains .blob-expanded, if that is the case, run run again. Should this be a function in octo-linker.js, or something? I can make a PR tomorrow.

[stefanbuck]

Great news 👍 Yes, putting that into octo-linker.js sounds appropriate to me. Regarding testing, recently I added E2E testing which should make testing such behaviour much easier. Literally, it's just click and inspecting the DOM for new .octolinker-link elements. I'm happy to help you if you get stuck.