Skip to content

Conversation

@PerthCharern
Copy link
Contributor

  • Fix the serialization and deserialization logic for V2 formData and body parameter.

  • V2 operation deserialization now respects the consumes property.

  • Unit tests verify that serializing, deserializing, and re-deserializing all work as expected.

Fix #178
Fix #179

… body parameter.

- Unit tests verify that serializing, deserializing, and re-deserializing all work as expected.
@PerthCharern
Copy link
Contributor Author

cc @talamram

}
};

var consumes = context.GetFromTempStorage<List<string>>("operationconsumes") ??
Copy link
Member

Choose a reason for hiding this comment

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

It is worth noting that this will import a valid V2 document correctly, but it will also create an invalid DOM if the media type is not a valid one. Validating this is going to be tricky, so I'm ok if we punt on checking for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree. It’s a bit complicated to add “validation logic” into the reader at this point. I’d rather wait for your PR to be completed and we can retroactively clean-up these validation grey areas later.

@PerthCharern PerthCharern merged commit d639dd5 into master Jan 22, 2018
@PerthCharern PerthCharern deleted the PerthCharern/FixFormData branch January 24, 2018 22:35
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.

3 participants