[Host.HybridMessageSerialzier] #238 Resolve HybridMessageSerializer dependencies from IServiceProvider [Alternative implementation]

[EtherZa]

As discussed in #238, here is an alternative implementation based on specialised builders for the hybrid message serializer.

As with all things, there are a few pros and cons

Pros:

• Implementation does not manipulate the DI which should result in no hidden surprises
• Builder code maintenance should be simpler (far simpler code required)
• Easier to add custom (unpackaged) registrations (can also exclude action is registered with container elsewhere)

  builder
  .RegisterSerializer<SerializerTwo>(services => services.AddSingleton<SerializerTwo>())
  .For(typeof(SampleTwo));

• No potential runtime exceptions due to state of builder not being as expected (won't compile on a misplaced .For())
• Intellisense shows what's available and nothing else

Cons:

• The hybrid message serializer becomes a special implementation requiring its own interfaces and implementation in other (unrelated) serializers
• Functionality needs an extra extension method to be added when adding a message serializer (old one remains, so it won't be a breaking change though)

[sonarcloud[bot]]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
83.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud