jab VS UrlActionGenerator

Having the same issues trying to get into source generators. I don't see too many opportunities to include it in my day-to-day development, or at least with the examples I've seen thus far. The exception being the dependency-injection based ones like https://github.com/pakrym/jab

There's also this https://github.com/pakrym/jab. Though imo, it has some downsides as well. One being less developer friendly when composing things compared to the current registration style and there's also convention based registration that so far isn't as easy to make.

Indeed! They're still early, but source generators can enable this sort of functionality, eg: https://github.com/pakrym/jab

There are some cases where it's really nice to eliminate magic strings. Here's one simple example nuget that auto generates calls to endpoints so you don't have to use magic strings for url generation in MVC. It's not as grand as the samples of using it on Serializers or DI but it does make it possible for small QOL things like these. This could even be extended to things like Blazor to autogenerate the backend's Rest endpoints to avoid hard coding url strings on httpcalls and make sure it's always in sync with the backend's endpoints.

Just click on Source Repository on the NuGet page, but here's the repo: https://github.com/sleeuwen/UrlActionGenerator