Skip to content

Conversation

@shimks
Copy link
Contributor

@shimks shimks commented Apr 26, 2018

Checklist

  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Documentation in /docs/site was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in examples/* were updated

const coercedParamArgs: OperationArgs = [];
for (const arg of paramArgs) {
debug('Coercing parameter', arg);
coercedParamArgs.push(typeof arg === 'object' ? arg : coerce(arg));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strictly speaking, it's about deserializing parameters from an http request. We have to respect the parameter type spec as illustrated in #941.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense, I was working on using the deserializers from @repository and was really wondering why we couldn't use a simple coercer. I'll revert this to what it is in the original PoC

@shimks
Copy link
Contributor Author

shimks commented Apr 26, 2018

Not in line with what coercion entailed; it needs to use the OpenAPI v3 spec. Closing in favor of #1256 (which may be divided up).

@shimks shimks closed this Apr 26, 2018
@shimks shimks removed the review label Apr 26, 2018
@bajtos bajtos deleted the http-coercion branch June 5, 2018 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants