Nicke Broström

Maybe you could allow the user to pass a `ElementReference` for content. That should be a Node when recieved by JS. https://blazor-university.com/javascript-interop/calling-javascript-from-dotnet/passing-html-element-references/

Well from what I can see you are just passing the string ´await CreateDiv(innerHTML)´? We would have to have something that overrides the call to `CreateAdvancedMarker` and calls that method...

A ElementReference is serializable though? Alteast when passing to JS. Should be possible without a workaround. I will try tomorrow. 😄

Oh I have completely forgotten about it. This solution looks fine, maybe i'll get some more time soon and can try to do the elementReference. The "non-duplication" thing sounds like...

This is a somewhat known issue if I am not mistaken, see #191 with a difficult solution and not a lot of time going around to fix it.

Hi! Though about the problem when going to bed last night and had to get up to try it. 😄 Agree that `DynamicProtocol` is not a optimal name. Might have...

Exactly like that! 😆 Ended up just trying to connect to different brokers and changing my protocol version. Most of them just worked. Tried to go though some HiveMQ code...

Agree that there is room for improvement. As for your example there, does that really make it simpler? In my opinion that feels a bit more difficult? Maybe my toml...

Not bad at all. This would be a breaking change right? Will look into implementing it later today! Any idea about how the type for this would look?

I'll change it to SupportedProtocol instead of SubProtocol to keep it clean until we actually change it. 👍🏼