I just looked at a bunch of libraries that do dependency injection in Go. Previously, I knew this concept from PHP where your request responders would get additional function parameters to do stuff based off of what the router did before and I was highly skeptical if Go could really do that.
... turns out, it can. And, I genuenly like the approach taken:
GitHub
GitHub - muir/npoint: dependency injection wrappers for binding http endpoint handlers
dependency injection wrappers for binding http endpoint handlers - muir/npoint
Might have to re-think how I do certain stuff. But for now, my biggest "worry" is how to optimize HTMX rendering. Like, I do not want to re-render an entire page if I don't have to, so I am trying to see what the dude behind templ thinks. There is a GH discussion about fragments and registering those to the context and then just rendering out the specific component fragment.
I feel like something is happening in my dev-mind and it will need time to brew. But once it is done brewing, I should have a pretty neat and nice stack - for both Nostr things and my own personal stuff (like the Dragon's Inn...which will also use Nostr, because I am lazy xD).
Ah... it feels good to be in the swing of dev stuff again. ^-^
