earloc

An alternative approach could be to let the `source-generator` scan referenced assemblies for existence of any present occurence of the generated extension method and incorporate it within its own generation....

@HaydnDias [v1.19.0](https://github.com/microsoft/kiota-dotnet/releases/tag/v1.19.0) just arrived and adds opt-in support for reading "numbers as strings". We had a similar situation of misbehaving APIs. While figuring this out, I also struggled a bit...

Totally agree on 1. and 2. (despite having a way to maybe pick a preference would be nice). 3. IMHO is not enough, as one would also need to derive...

@baywet so here's why it's currently a bit difficult to "just derive from `JsonParseNode` and override it". 1. theres actual no `virtual` member, to plugin custom behavior 2. even when...

question: how to ensure there is a `IStringLocalizer`?

@khellang I thought about coming up with some code-gen for generating registrations at compile-time, so assembly scanning might shift left (to compile-/design-time). I love how this lib eases up service...

Nice, @khellang! Got some hands on with source-generators lately over at https://github.com/earloc/TypealizR. So my current "bad" gut feeling tells me, that doing assembly scanning within a source-generator might turn into...

just had a glance over the changes in #129 and tbh, I don't get the concept behind it ;) (but also wouldn't bother to at least try, either :) )

Thinking about this, it might also turn into a direction, where we would "just" need a roslyn-capable implementation of `ITypeSourceSelector ` (and everything beneath), which would only need to surface...

Hey @khellang. I think I managed to come up with a workable POC on how to use user-defined code to influence the behavior of a source-generator. In a nutshell: Aiming...