+1
that's a great way to state it Sam.
regards,
mike
- Original Message -
Hi Amit,
Keeping in mind this viewpoint is nothing but my own personal view, my
recommendation would be to not mandate the use of a particular validation
framework, but to instead define what kind of
Thanks for the clarification Sam.
Its good to know where the mission of the API working group starts and
stops. During the meetup discussions, my understanding was that the
working group would recommend the technologies to use while building apis
(e.g. Pecan, validation frameworks, etc) and were
On 10/20/2014 10:26 AM, Amit Gandhi wrote:
Thanks for the clarification Sam.
Its good to know where the mission of the API working group starts and
stops. During the meetup discussions, my understanding was that the
working group would recommend the technologies to use while building apis
On 10/20/14, 10:38 AM, Jay Pipes jaypi...@gmail.com wrote:
On 10/20/2014 10:26 AM, Amit Gandhi wrote:
Thanks for the clarification Sam.
Its good to know where the mission of the API working group starts and
stops. During the meetup discussions, my understanding was that the
working group
On 20 October 2014 15:38, Jay Pipes jaypi...@gmail.com wrote:
On 10/20/2014 10:26 AM, Amit Gandhi wrote:
Thanks for the clarification Sam.
Its good to know where the mission of the API working group starts and
stops. During the meetup discussions, my understanding was that the
working
On Mon, 20 Oct 2014 10:38:58 -0400
Jay Pipes jaypi...@gmail.com wrote:
For stackers who are interested in different validation frameworks
to implement validation, I recommend checking out Stoplight.
Just my two cents on this particular topic, I think it's more
important to standardize
Hi Amit,
Thanks for picking this topic up,
Honestly I don't have a strong opinion about validation libraries.
Each project implements based on different web frameworks and
the options of validation libraries would be limited from its web
framework. For example, Nova implements its own wsgi
- Original Message -
However I don't think we should be mandating specific libraries, but we
can make recommendations (good or bad) based on actual experience. This
will be especially useful to new projects starting up to benefit from
the pain other projects have experienced.
+1
i
On Tue, Oct 21, 2014 at 12:15 PM, Kenichi Oomichi oomi...@mxs.nes.nec.co.jp
wrote:
Hi Amit,
Thanks for picking this topic up,
Honestly I don't have a strong opinion about validation libraries.
Each project implements based on different web frameworks and
the options of validation
Hi Chris,
2014-10-21 13:41 GMT+09:00 Christopher Yeoh cbky...@gmail.com:
On Tue, Oct 21, 2014 at 12:15 PM, Kenichi Oomichi oomi...@mxs.nes.nec.co.jp
wrote:
Hi Amit,
Thanks for picking this topic up,
Honestly I don't have a strong opinion about validation libraries.
Each project
Hi Amit,
Keeping in mind this viewpoint is nothing but my own personal view, my
recommendation would be to not mandate the use of a particular validation
framework, but to instead define what kind of validation clients should expect
the server to perform in general. For example, I would expect
11 matches
Mail list logo
