We have developed an engine that combines a RAML API definition along with some reflection on the backend which allows us to dynamically link/expose platform services as APIs as defined in the RAML ‘contract’
All is well except for one little (big) headache.
Uri/Query Parameters are restricted to the above types whereas i need to have any number of custom types. An example is for say CardNumbers i’d define a “cardnumber” type - which would save me a some work on the backend in terms of conversion, !logging etc.
Why is this check in place? is there any way to remove it? or at least extend the valid set of types?