You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -63,7 +63,7 @@ We are actively expanding the feature set and fixing bugs; this documentation wi
63
63
64
64
When you hover over a keyword (node key) in the document, the extension shows full, context-aware documentation in a hover panel that corresponds to the selected construct and matches the official specification.
The same documentation is also shown in the details pane of completion items. See the “Completion / Suggestions” section below. 
@@ -77,20 +77,20 @@ OpenAPI Toolkit provides an enriched completion experience. Under the hood, comp
77
77
Each completion item includes full documentation (the same content shown in hover).
78
78
**Tip:** If the documentation panel doesn’t appear to the right of the completion label, click the `>` icon that appears when you hover the completion entry. 
When completion is triggered within the value of a `$ref` field, the editor offers suggestions of compatible targets found in the document (this will be expanded to include documents across the workspace). It also displays the referenced content in the completion box, providing an in-context view of potential references without losing focus 
@@ -99,41 +99,41 @@ Suggestions adapt to related fields. For example, if a schema sets `type: intege
99
99
100
100
Hovering over the value of a `$ref` field displays the referenced content in the hover box, providing an in-context view of references without losing focus. 
Right-click the value of a `$ref` field and choose **Go to Definition** (or press **F3**) to jump to the reference target—either within the current file or in another file in the workspace. 
Right-click a key (for example, under `components.schemas`) and choose **Go to References** to open a panel listing available references to jump to. 
Right-click a key (for example, of a schema) and choose **Find All References** to open the References panel listing every usage of the selected target. 
Right-click inside an OpenAPI document or right-click the file in the Explorer, then choose **OpenAPI Toolkit → Dereference API Document** to save a dereferenced copy locally. The default output name is `{filename}-dereferenced.{extension}`. 
OpenAPI Toolkit provides **semantic** syntax highlighting, going beyond basic keyword coloring. Specific OpenAPI elements—such as operations, schemas, and reference objects—are highlighted with distinct colors and font styles. This helps you quickly recognize and distinguish different parts of an API definition, improving readability and navigation in complex specifications. 
0 commit comments