Type Name Overhaul

[zac]

I've gone through the types we use in Endpoints and wanted to unify some naming and clarify some usages.

The biggest change is the renaming of RequestType to Endpoint and the Endpoint type to Definition. So now you create a type conforming to Endpoint which includes a static propertyDefinition and the data and components that plugs into the definition. That felt more appropriate given the name of the library, but open to suggestions for other conventions.

Other renames include:

• Parameters and HeaderValues to ParameterComponents and HeaderComponents respectively. The idea with this change was to name all the data that gets defined in the Endpoint with the suffix 'components' since they are pieces that plug into the Definition
• EmptyResponse to EmptyCodable. This was to resolve some confusion since EmptyResponse is used as the Body by default... which isn't a response at all.
• Headers to Header since it represents a single header.

Still weighing some alternatives though:

• Empty could be better named EmptyCodable since that's basically what it is (I went ahead and made this change)
• ErrorDecoder could be ErrorResponseDecoder to match other decoder type names
• In other places I've removed the Type suffix from protocols, but not for the EnvironmentType case. Could shorten that to just Environment, but that might interfere with SwiftUI annoyingly in some projects. Perhaps we should use a completely different name? Or ServerEnvironment? EndpointEnvironment?

I tried to update the documentation to match, but let me know if you see any issues!

[weilikuo]

👍

I'll create a task on Acrylic to migrate to the updated Endpoints