vittoriom / rnfplaceholder Goto Github PK

An endpoint should have default queryString parameters (e.g. the api_token to use) that should be included in all the operations

It should be able to parse all the parameters of Endpoint, Operation (, Deserialization, ... ) configurations with the same shared logic (use of named parameters and parameters from the runtime call).

It should also be able to merge parameters of an operation with the ones from the endpoint.

Upload GDocs (Configuration documentation and Architecture Diagram + more) on GitHub Wiki

Contestually provide a concrete implementation and attach the behavior to the endpoint

e.g. dataDeserializer, responseValidator, dataSerializer and so on. For the plist case, it would be nice to define everything inline, specifying the class to instantiate and some parameters, that could be then forwarded to the class either through a dictionary, or through dynamic calling of a method

The component should take a parameter key and merge the values of the operation configuration with the ones of the endpoint configuration, if any

Contestually provide a concrete implementation and attach the behavior to the endpoint

Contestually provide a concrete implementation, write tests and attach the behavior to the parameter parser

Contestually provide a concrete implementation and attach the behavior to the endpoint

So that the AppleDoc doesn't contain reference for it.

In case the element is valid, the request won't be forwarded to the network

The user can set values in the Endpoint configuration, such as:

API_TOKEN : @"asf3q32tw4lk"

and these can be used in the URLs of the operations

Every subproject should be usable on its own, the master project should use the sub-projects without issues

Make them similar to dataDeserializer, dataSerializer and so on (returning an instance instead of a Class)

The parameter can also be specified at the endpoint level, and in case the values will be merged, with the operation having priority.
Values can be specified as single HTTP codes:
success : 200
or as ranges
success : 200-300
or as multiple values
success: 200,202-205

Contestually provide a concrete implementation and attach the behavior to the endpoint

Operations should be serializable

If not, fallback to the completion block

The component should be responsible of validating a response, after it's been deserialized (but before the dataSerializer has kicked in).
For example it can check for specific HTTP codes, or inspecting the response to search for specific patterns (e.g. a JSON object containing "errors" array).

Contestually provide a concrete implementation for both protocols to use as a default and attach the behavior to the endpoint

Contestually provide a concrete implementation and attach the behavior to the endpoint

Implement RNFBaseOperation (simple behavior) by using Cocoa classes.

Contestually provide a concrete implementation and attach the behavior to the endpoint

Contestually provide a concrete implementation and attach the behavior to the endpoint/operation