Use Source Generators for Serialization/Deserialization

[Velociraptor45]

As .net continuously moves in the direction of AoT compilation, it would be great to support non-reflection based serialization & deserialization through source generators.

I had a quick stroll through the codebase, and it should be possible to implement I'd say. The only tricky parts are

• The Dictionary<string, object> as object can be anything and the Serializer needs to have the exact type in its source generator registered. I haven't looked that deep into it, but maybe the object types are mostly string or at least generally known?
• The generic T response deserialization where the user can provide any T (e.g. ReadSecretAsync<T>), but this then has to be configured by the users themselves - maybe by registering their own custom TypeInfoResolver?

Would be great if you could consider this. Thanks!

[rajanadar]

thanks @Velociraptor45 for bringing this up.

At this point, there isn't much ROI in VaultSharp for this feature.
No concerns on JIT time for a simple library, difficulty of dealing with Dictionary which is very rampant in the Vault data model, machine specific binaries etc.

When an ROI case comes up, i'll definitely think through a real option.

[bbartels]

This would mostly be beneficial in situations where this library is used in projects that are AOT and want to use vaultsharp, not necessarily that vaultsharp sees many benefits of that @rajanadar

[bbartels]

I have created: #394. It is now ready for review!