Implement payload validation for endpoints

[mbillow]

Flask probably has a decorator for this or someone has probably already implemented it. Will investigate and implement.

[liam-middlebrook]

By this do you mean return a JSON object and HTTP status code as applicable? I'm not sure how wrapping each POST method in exception handlers would be verbose enough about specific errors that occur with input data.

On Aug 4, 2016, at 7:26 PM, Marc Billow notifications@github.com wrote:

Flask probably has a decorator for this or someone has probably already implemented it. Will investigate and implement.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[mbillow]

I wasn't looking for something that generic, but I haven't found anything that would specifically meet our needs. I want to implement reasonable error codes and it looks like doing it manually is the only decent way.

[stevenmirabito]

With our current implementation, we would have to implement this manually. However, I'd much prefer that we use a framework such as Potion that would help us solve both this issue and #18.

Since we don't currently have any third-party consumers of our API and resolving this would involve a lot of manual refactoring either way, I would recommend we push this work off to v2.

[liam-middlebrook]

I'm not sure that using something like Potion is a good idea for v1.0. I think for now manually creating prechecks for POSTed data is sufficient and then for v2.0 we can switch over to something like Potion.

On Aug 6, 2016, at 11:20 AM, Steven Mirabito notifications@github.com wrote:

With our current implementation, we would have to implement this manually. However, I'd much prefer that we use a framework such as Potion that would help us solve both this issue and #18.

Since we don't currently have any third-party consumers of our API and resolving this would involve a lot of manual refactoring either way, I would recommend we push this work off to v2.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.