How should providers be configured or built?

[tacosontitan]

One of the biggest problems Pasper has to solve is how to support native provider attributes along with custom ones. A solid idea to facilitate this is to configure which attributes are favored in the serialization process instead of forcing consumers to always utilize what Pasper offers.

One idea is to use the builder pattern to construct providers, or at least their configurations to ensure that consumers can utilize what their ecosystems already employ without a major facelift to their codebase.

A simple and very rough snippet is:

public static ISomething ConfigureXmlProvider(ISomethingElse configuration) => configuration
    .SerializeAttributesWith<XmlAttributeAttribute>()
    .SerializeCollectionsWith<XmlArrayAttribute, XmlArrayItemAttribute>()
    ...
    ;

I don't really like the verbosity of the methods here, so more thought needs to be given to how these methods should be defined and supported within provider abstractions.