Ted Epstein

@satykrishna , we have seen a similar error in RepreZen API Studio, our commercial solution, which includes KaiZen Editor as a component. But we have not seen this in cases...

Parameters are by far the most common stumbling block for this issue. The rules for different parameter locations (as determined by the `in` property value) are very different, and error...

Note: The current draft of JSON Schema includes `if`, `then`, and `else` keywords as [described here](http://json-schema.org/latest/json-schema-validation.html#rfc.section.6.6). We could use this to implement discriminator-like logic. And a validating parser that works...

@tfesenko , can the suggestion be context-sensitive, so we have something like `(property name)` in the context shown, and some other appropriate label in other contexts?

@tfesenko , @ghillairet , I'm placing high priority on this one, though I don't necessarily think we should jump into implementation. There are some things we should probably do first,...

@tfesenko , this looks good! We have to somehow communicate that "schema" in the proposal list is not a keyword; it's a placeholder for a schema name that the user...

@tfesenko, this should also work for properties of object schemas. Same problem in the current editor:  In this context, we want to propose `(property name)` in code assist and...

@tfesenko , I updated the [spec above](#issuecomment-331507964) with additional context-sensitivity requirements. We will need to discuss the timing of this, as the full scope of work to be done is...

Hi @3DRaven , I am not sure I am following your scenario correctly. I'll ask some specific questions here: > When used $ref to external file with definition: So you...

I see. Somehow your example.yaml file has been recognized incorrectly as a Swagger 2.0 document, when it is really just a YAML document, not intended to follow the full Swagger...