## Description / Steps to reproduce / Feature proposal For DP3, we'd like validation and coercion system implemented in the http-layer to use `@loopback/types` ## Acceptance Criteria - [ ] Move `types` folder from `@loopback/repository` into its own package; Make sure this PR is refined and make sure it lands https://github.com/strongloop/loopback-next/pull/947 - [ ] Move over the converters used in http coercion into appropriate files in `@loopback/types` with extensibility in mind. - [ ] Come up with a decorator system (`@param` or a new one if necessary) to introduce metadata to appropriately infer type metadata (for example Date) <!-- HELP US HELP YOU, PLEASE - Do a quick search to avoid duplicate issues - Provide as much information as possible (reproduction sandbox, use case for features, etc.) - Consider using a more suitable venue for questions such as Stack Overflow, Gitter, etc. --> _See [Reporting Issues](http://loopback.io/doc/en/contrib/Reporting-issues.html) for more tips on writing good issues_