Issues with Content-assist about kaizen-openapi-editor HOT 9 CLOSED

path value for method parameters in

Line 26 of the default model defines the "path" value. However, content-assist does not provide it.

        in: "path"

from kaizen-openapi-editor.

"$ref" key not provided by content-assist

UPD: now it works

Line 34 of default model:

          schema:
            $ref: "#/definitions/TaxFilingObject"

from kaizen-openapi-editor.

type keyword in definitons and properties

There is no code assist for type value of definition or property, e.g.

definitions:
  TaxFilingObject:
    type: "object"

and (for filingID)

  TaxFilingObject:
    type: "object"
    description: "An individual Tax Filing record, accessed by its ID"
    properties:
      filingID:
        type: "string"

Parameters type works fine.

from kaizen-openapi-editor.

Content-assist for value of schema/$ref

It would be good to provide content assist for responses/schema/$ref which would calculate available refs to definitions.

from kaizen-openapi-editor.

path value for method parameters in issue

It is solved in this pull request:
#34

Content-assist for patternProperties

This raises the question about how we should handle pattern properties, and if we should introduce specific implementation for some of them. Some pattern properties are fine to be use as replacement strings, see below for example on path, some are not like for responses code, that uses regex strings.

refs issues

The refs issues are a bit different and involves two different cases:

• The first is about resolving references to external json schema documents. The swagger schema references standard schemas from json-schema.org, and we should include those during generation of the content assist.
• The second is about showing the user possible references that can be used as values for the keys $ref in the document being edited. This can be could primarily by proposing the user, elements present in the definitions object of the current document.

We should open different issues for those different cases.

from kaizen-openapi-editor.

Some fixes for the issues related to refs have been pushed in branch external-refs.

Content assist now provide proposals for references inside the document, that is only for elements defined in definitions

Content assist also provides more hints about types of elements, as it is now able to parse external schemas.

from kaizen-openapi-editor.

Tanya will extract these to separate issues.

from kaizen-openapi-editor.

@tfesenko , FYI, I just read through the comments here. The most important issues are already fixed.
"Content-assist for patternProperties" should be extracted to a separate issue. Not sure right now how we should handle that.

from kaizen-openapi-editor.

Extracted #70 Content-assist for patternProperties .
Closing this issue

from kaizen-openapi-editor.