This repository was archived by the owner on May 16, 2022. It is now read-only.
Add explicit formatter declaration for ZeroFormattable attribute #81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I find it rather complicated having to register the formatters one after one. First, advanced logic is needed to register all resolvers from all referenced libraries (were should that code be put?) and it's uneconomical to keep track of all needed resolvers in a huge repository. I implemented a behavior like Json.Net and XmlSerializer are using: Every type knows it's formatter which is just used instead of resolving one (if it's set). The registering still has it's use when dealing with external types, but for custom types the
FormatterType
is a huge advantage.