This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

Distinguish business warnings from HTTP spec violations #51

Closed

zdne opened this issue Oct 22, 2013 · 1 comment

Labels

Milestone

HTTP Validation

Contributor

zdne commented Oct 22, 2013

Usually parser warnings are treated very seriously; maybe differ between business error and HTTP spec violation

zdne added this to the v1.0 milestone

zdne mentioned this issue

Response status should default to 200 apiaryio/api-blueprint#42

Closed

zdne mentioned this issue

Snowcrash should warn when blueprint specifies Request with GET method #64

Closed

zdne added this to the HTTP Validation milestone

This was referenced Oct 1, 2018

Snowcrash should warn when blueprint specifies Request with GET method apiaryio/drafter#622

Open

Distinguish business warnings from HTTP spec violations apiaryio/drafter#624

Open

Snowcrash should warn when blueprint specifies Request with GET method apiaryio/drafter#646

Open

Distinguish business warnings from HTTP spec violations apiaryio/drafter#648

Closed

Contributor

abtris commented Oct 1, 2018

Migrated to apiaryio/drafter#648

abtris closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.