Web-Anchor

Web-Anchor copied to clipboard

replaces #71

So what does this actually entail? Creating a seperate nuget for those who only want to design an api-interface, to maybe expose as a nuget package. These guys obviously don't need code generation, apifactory (Api.For), anchor, httprequestbuilder etc. This change presses for some changes to the possibility of passing apiSettings to Api.For. What we pass in as settings is usually things that are closely tied to the implementation of the api, rarely or never settings that the client can actually chose on his own.... so, most (if not all) things in the apisettings must be available for the api designer.

What to move to WebAnchor.Core: HttpAttributes BaseLocation, Header and Alias-attributes, ContentAttributes (these are tied to implementations of serialization. The client designer doesn't need the implementation of the serializer, but might need to declare serialization options, to for example configure expected json-formats. This works very different for different json-serializer-implementations, so the api-interface is closely tied to the serializer-implementation anyways. What I'm saying is the consumer of the api-interface can't pick and choose between System.Text.Json and Newtonsoft anymore. Is this a problem? Should there be a way to override? Probably not, you could always write your own client completely.) ParameterTransformers? ApiSettings - how to declare on interface?