<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss/styles.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>API Genie editor releases</title><description>What changed in each release of the API Genie editor.</description><link>https://api-genie.dev/changelog/editor</link><language>en</language><item><title>API Genie editor 0.12.0</title><link>https://api-genie.dev/changelog/editor#0120-2026-11-08</link><guid isPermaLink="true">https://api-genie.dev/changelog/editor#0120-2026-11-08</guid><pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;The right pane has no Code tab. &lt;em&gt;Show as code&lt;/em&gt; on a file’s root form, such as the &lt;em&gt;Specification&lt;/em&gt; row’s, shows the
whole file as wide as the pane. While a file has syntax errors, its forms offer &lt;em&gt;Show the file as code&lt;/em&gt;. A file
picked in the file list opens its root form. The code no longer follows the tree’s selection, and its cursor no
longer selects in the tree.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;With one spec open, the tree starts with a &lt;em&gt;Specification&lt;/em&gt; row that opens the whole spec’s form: its version
and its sections. The form is headed &lt;em&gt;Specification&lt;/em&gt;, in place of &lt;em&gt;Document&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In a schema’s rows, the type menu keeps its width and the description takes the rest. A long component name
among the menu’s references made the menu as wide as the name.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A long form, such as an operation’s, lists its sections beside it: pick one to go to it, or &lt;em&gt;Overview&lt;/em&gt; to go back
to the start of the form. The list marks the section you are reading and hides when the form is narrow.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;AsyncAPI’s forms, such as a message’s, list their sections as well.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A schema’s form lists its sections too: the details of the row shown, in groups (Values, Limits, Flags,
Composition) now headed in the details panel, and the keys edited as code.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Each key a form has no field for, such as &lt;code&gt;externalDocs&lt;/code&gt; or a parameter’s &lt;code&gt;style&lt;/code&gt;, is a section of its own,
named after the key and edited as code, in place of one &lt;em&gt;Other fields&lt;/em&gt; section.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The forms’ section headings, such as Parameters, Request body, Responses and Messages, are bands with an accent
edge, set apart from the fields above them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The parameters table’s &lt;em&gt;In&lt;/em&gt;, &lt;em&gt;Required&lt;/em&gt; and &lt;em&gt;Schema&lt;/em&gt; columns grow with their text in Safari and the macOS app, where a
header parameter’s &lt;em&gt;header&lt;/em&gt; ran into &lt;em&gt;yes&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The code view, &lt;em&gt;Show as code&lt;/em&gt; and the text diffs use CodeMirror in place of Monaco: the
app’s code is less than half its former size, about 4.5 MB instead of 10 MB. Completion and hover still come from
the spec’s structure, and now work while the line you type is not valid YAML yet. The editor’s colours follow
the app’s light and dark palettes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;YAML is highlighted in the code view and in a form’s &lt;em&gt;Show as code&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;File › Close Spec (Ctrl+W, Cmd+W on macOS) closes the open spec and the files it brought, asking about unsaved
changes first. The editor is then as it starts with no spec.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A &lt;em&gt;New spec…&lt;/em&gt; button joins the toolbar. With no spec open, it asks for OpenAPI 3.1 or AsyncAPI 3.0, as File ›
New… does, then where to save the spec. The editor writes the spec there and opens it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;File › Open Recent lists the last ten specs opened, then Clear Recent. Started without a spec on the
command line, the editor opens the newest one that still exists.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Files changed on disk, by a &lt;code&gt;git checkout&lt;/code&gt; or another editor, are read again when you come back to the window.
A file with unsaved changes keeps them: the status bar names it, and Save writes over the version on disk. A
file deleted on disk is named in the status bar.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A View menu shows and hides the Side Bar (Ctrl+B), the Panel (Ctrl+J) and the Right Pane (Ctrl+Alt+B); on
macOS, Cmd+B, Cmd+J and Cmd+Option+B. With the panel closed, the form and the right pane now reach the status bar.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Export bundled&lt;/em&gt; works in the desktop app for OpenAPI specs, and the Changes tab shows the API changes there.
The installers now carry &lt;code&gt;openapi_bundle&lt;/code&gt;, &lt;code&gt;openapi_diff&lt;/code&gt; and &lt;code&gt;asyncapi_diff&lt;/code&gt;, compiled to WebAssembly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The splitters between the panes are thicker, with a grip in the middle.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A path’s template and its path parameters change together in the forms. Each change is one undo step. A
change that would give the path another path’s template is refused, and nothing changes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Setting a parameter’s &lt;em&gt;In&lt;/em&gt; to &lt;em&gt;path&lt;/em&gt; makes it required and adds &lt;code&gt;/{name}&lt;/code&gt; at the end of the template.&lt;/li&gt;
&lt;li&gt;Renaming a path parameter renames its &lt;code&gt;{name}&lt;/code&gt;, and the other path parameters of that name in the path and
its operations. A name another path parameter already has is refused.&lt;/li&gt;
&lt;li&gt;Removing a path parameter, or setting its &lt;em&gt;In&lt;/em&gt; to another place, takes &lt;code&gt;{name}&lt;/code&gt; out of the template
(&lt;code&gt;/pets/{id}&lt;/code&gt; becomes &lt;code&gt;/pets&lt;/code&gt;). It stays when another path parameter of the path or its operations has that
name.&lt;/li&gt;
&lt;li&gt;The path’s form and an operation’s form do all three. A parameter’s own form renames it and sets its &lt;em&gt;In&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;Editing the template in the path’s form renames, adds or removes path parameters to match. A new &lt;code&gt;{name}&lt;/code&gt;
gets a required string path parameter on the path. When as many &lt;code&gt;{name}&lt;/code&gt;s go as come, they are read as
renames, in order.&lt;/li&gt;
&lt;li&gt;Renaming a path parameter or editing the template leaves the parameters taken by &lt;code&gt;$ref&lt;/code&gt; as they are.
A rename then keeps their &lt;code&gt;{name}&lt;/code&gt;, and a &lt;code&gt;{name}&lt;/code&gt; of theirs renamed in the template gets a new path
parameter.&lt;/li&gt;
&lt;li&gt;In the path’s form, a path parameter of the path or its operations that the template lacks has a button,
&lt;em&gt;Add {name} to the template&lt;/em&gt;, which adds &lt;code&gt;/{name}&lt;/code&gt; at the end.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The tree lists these sections even when the spec lacks them: Servers, Tags, Paths, Webhooks (3.1 only) and
Components in OpenAPI; Servers, Channels, Operations, Messages and Components in AsyncAPI. Each section,
and each component section under Components, has a &lt;em&gt;+&lt;/em&gt; that adds an entry and selects it, so that its form
opens. A section the spec lacks is created with that entry. The &lt;em&gt;+&lt;/em&gt; of Components asks which kind of component
to add. The right-click menu has the same items, such as &lt;em&gt;Add server&lt;/em&gt;, &lt;em&gt;Add operation…&lt;/em&gt; and &lt;em&gt;Add schema&lt;/em&gt;, and
Insert on a focused row does what its &lt;em&gt;+&lt;/em&gt; does. Shift+F10 opens that menu on keyboards without Insert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The &lt;em&gt;+&lt;/em&gt; of Paths asks for the method and the path of a new operation, and offers the paths the spec has, so
that one path can get several operations (&lt;code&gt;GET /pets&lt;/code&gt; and &lt;code&gt;POST /pets&lt;/code&gt;). A new path is created with its
operation. The right-click menu of an operation, and of a path without operations, has &lt;em&gt;Add operation to
/pets…&lt;/em&gt;, which starts with the path’s first free method, and Insert on such a row opens it too. Adding a
method the path already has, or a path of the same shape as one the spec has (&lt;code&gt;/pets/{petId}&lt;/code&gt; beside
&lt;code&gt;/pets/{id}&lt;/code&gt;), says so.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The forms of a path item (a path, a webhook, a callback’s path or one under Components) and of an operation
have &lt;em&gt;Delete…&lt;/em&gt; in their header. It asks first, names the references that would break, deletes as one undo
step and opens what held the deleted entry. The right-click menu of an operation under Paths has &lt;em&gt;Delete path
/pets…&lt;/em&gt; too, since the tree lists a path with operations only through them; for a path that is a &lt;code&gt;$ref&lt;/code&gt;, it
deletes the path and keeps what the path refers to.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The forms of a tag, a server and every component (a schema, response, parameter, example, request body,
header, security scheme, link or callback, in AsyncAPI too) have the same &lt;em&gt;Delete…&lt;/em&gt;. Deleting a tag leaves
the operations that list it as they are, and the confirmation says how many do.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A server variable’s &lt;em&gt;Values&lt;/em&gt; are chips, as an operation’s tags are: Enter or a comma adds a value, its × removes
it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A schema’s &lt;em&gt;Allowed values&lt;/em&gt; are chips, as a server variable’s values are. In a numeric or boolean schema a typed
&lt;code&gt;3&lt;/code&gt; or &lt;code&gt;true&lt;/code&gt; is added as a number or a boolean, and the values already in the file keep their types. An object
or array schema keeps the YAML text field.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Values chips no longer leave an empty line under them: the input after the chips takes what is left of their line.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Every example box (a schema’s or a property’s example, an Example object’s value, a media type’s and a
message’s examples) has a copy button in its top right corner. It copies the example as shown, JSON or YAML.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A form’s header shows where its node is, from the file down (&lt;em&gt;openapi.yaml › Paths › /pets › GET ›
Responses › 200&lt;/em&gt;), in place of its JSON pointer, which is now the tooltip. Each step opens that node’s form.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The parameters tables of a path and an operation size their columns to what they hold: &lt;em&gt;In&lt;/em&gt;, &lt;em&gt;Required&lt;/em&gt; and
&lt;em&gt;Schema&lt;/em&gt; are as narrow as their content, &lt;em&gt;Name&lt;/em&gt; takes a fifth of the width and &lt;em&gt;Description&lt;/em&gt; the rest.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The tree’s sections each have an icon (Info, Servers, Tags, Paths, Webhooks, Components, Channels, Operations,
Messages), and so do the spec, shared-file and import-only groups.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Example fields show the value as JSON, with a switch to YAML that is kept for the next examples. These are the
Example of schemas, parameters and media types, an Example’s Value (formerly &lt;em&gt;Value (YAML)&lt;/em&gt;), and a message
example’s payload and headers. A value with &lt;code&gt;.inf&lt;/code&gt;, &lt;code&gt;.nan&lt;/code&gt; or a recursive alias, which JSON can’t hold, stays in
YAML. Either is read back, and the file keeps its own style.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A schema’s details show its Description, in Markdown with a Write / Preview switch.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A schema row’s type menu offers one of, any of and all of, and a reference to each component schema.
A schema the menu cannot show (several types, &lt;code&gt;not&lt;/code&gt;…) reads &lt;em&gt;complex&lt;/em&gt;, and &lt;em&gt;Edit in code&lt;/em&gt; opens it in
the code view.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The Example field of a schema’s details is multi-line, and the other YAML fields there keep the lines of a
mapping or a list: a generated object example no longer shows (and saves) as one joined line.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;An operation’s tags are a multi-select: chips that remove themselves, and an input that adds a tag,
suggesting the declared ones.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The Problems panel filters by severity (Errors, Warnings, Info, Hints), and keeps the choice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A form shown as code fills the height of the form pane.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The file list is headed &lt;em&gt;Spec and referenced files&lt;/em&gt;, and the form’s Raw section is split into &lt;em&gt;Other fields&lt;/em&gt;
and &lt;em&gt;Extensions&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The desktop app lints OpenAPI documents with API Genie’s own linter (the rules of &lt;code&gt;apigenie lint&lt;/code&gt;), in the
Problems tab and under the fields, with its quick fixes: the installers now carry it, compiled to
WebAssembly. Until now only the web editor had it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The linters read &lt;code&gt;commands.lint&lt;/code&gt; of the project’s &lt;code&gt;apigenie.yaml&lt;/code&gt;, and &lt;code&gt;commands.lint.asyncapi&lt;/code&gt; for AsyncAPI.
The editor takes the file nearest to the spec, as &lt;code&gt;apigenie lint&lt;/code&gt; run in the spec’s folder finds it. It looks in
the spec’s folder on the desktop and the workspace folder in VS Code; in a browser, among the dropped files. On
the desktop and in a browser, &lt;em&gt;Allow access to their folder…&lt;/em&gt; widens that to a folder above the spec. Rulesets, severities and custom rules apply in the editor. A configuration the linter refuses is an error
on the configuration file in the Problems tab, and then the default rules apply. Custom JavaScript functions don’t
run yet: the rules that call them are left out, with a warning. In VS Code an edit to the file applies as you
type; elsewhere a change applies when the spec is opened again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The linters read the ruleset files that &lt;code&gt;extends&lt;/code&gt; names in &lt;code&gt;apigenie.yaml&lt;/code&gt;, and the files those extend
(ADR-217): from the spec’s folder on the desktop; in a browser, from a folder allowed with &lt;em&gt;Allow access to their
folder…&lt;/em&gt;, or in Safari and Firefox among the dropped files when they sit beside &lt;code&gt;apigenie.yaml&lt;/code&gt;. Their functions
are left out with the rules that call them, and a warning says so. When a ruleset file
extends a ruleset the editor’s linter doesn’t have (&lt;code&gt;spectral:oas&lt;/code&gt;, &lt;code&gt;owasp&lt;/code&gt;, an npm package), that ruleset is
left out with a warning. A ruleset file’s &lt;code&gt;aliases&lt;/code&gt; and &lt;code&gt;overrides&lt;/code&gt; are skipped with a warning too. An &lt;code&gt;extends&lt;/code&gt;
entry with an absolute path, or a relative path more than 8 folders up, is an error on that entry, and so is a
ruleset file that can’t be read or doesn’t parse. The default rules then apply.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;AsyncAPI documents are linted with API Genie’s AsyncAPI linter (the rules of &lt;code&gt;apigenie lint&lt;/code&gt; for
AsyncAPI), with its fixes, in every host.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The editor no longer runs Spectral’s rulesets (&lt;code&gt;spectral:oas&lt;/code&gt;, &lt;code&gt;spectral:asyncapi&lt;/code&gt;) or a &lt;code&gt;.spectral.yaml&lt;/code&gt;. The
Problems tab shows the findings of API Genie’s linters under their own rule names, without Spectral’s second
report of the same problems. Spectral rules with no counterpart in API Genie are no longer reported. To keep a
&lt;code&gt;.spectral.yaml&lt;/code&gt;’s rules, move them to &lt;code&gt;apigenie.yaml&lt;/code&gt;: see
&lt;a href=&quot;https://api-genie.dev/docs/guides/migrate-from-spectral&quot;&gt;Migrate from Spectral&lt;/a&gt;. A Spectral ruleset (&lt;code&gt;.spectral.yaml&lt;/code&gt;,
&lt;code&gt;.yml&lt;/code&gt; or &lt;code&gt;.json&lt;/code&gt;) with no configuration file in the spec’s folder or above it gets an info finding that names
that guide.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;AsyncAPI documents are checked by API Genie alone (ADR-212): the AsyncAPI parser’s findings are gone, and
what it checked comes from API Genie’s AsyncAPI linter, which gains 5 rules for the parser’s core checks it
lacked (&lt;code&gt;apigenie lint&lt;/code&gt; reports them too). A structure error in another file of the spec shows on that file,
where the error is.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The AsyncAPI docs preview shows API Genie’s own AsyncAPI docs, as &lt;code&gt;apigenie&lt;/code&gt; publishes them: the overview,
servers and security of the spec, or the operation, channel or message selected in the tree or the code
view. It no longer loads the official AsyncAPI renderer, and the editor carries no React.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The editor opens specs, not folders (ADR-197). &lt;em&gt;Open folder…&lt;/em&gt; is gone: &lt;em&gt;Open spec…&lt;/em&gt; (File › Open Spec…,
Ctrl+O, on the desktop) opens a spec with the files it refers to. The desktop app starts on a spec given on
its command line (&lt;code&gt;apigenie-editor openapi.yaml&lt;/code&gt;), dropped spec files open in the browser, and a dropped
folder is refused. A new file never overwrites a file on disk the editor did not read: suggested names skip
it, and Save refuses and says why.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Open spec…&lt;/em&gt; opens one spec and the files its references reach, read as references name them, also
after an edit adds one (ADR-197). Files that can’t be read are listed under the file list, with &lt;em&gt;Allow
access to their folder…&lt;/em&gt; on the desktop and in Chromium browsers. In VS Code, the document is the spec
and only the files it reaches join it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The opened spec is the file being edited (ADR-197). The other files are referenced: shown in the tree, the
file list (under Referenced), the code view and Problems, but read-only, with &lt;em&gt;Edit this file&lt;/em&gt; to change
one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Path parameters have no Required checkbox: they are always required, and moving a parameter into the
path sets &lt;code&gt;required: true&lt;/code&gt; with the change.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Schema findings on examples, bindings and Try it name the field as code reads it (&lt;code&gt;[0].owner: Unexpected property &apos;age&apos;&lt;/code&gt;) instead of a JSON pointer and Ajv’s message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The editor fits its window: in a short window the bottom panel gives way, and the page never scrolls.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A tag’s form lists the operations that have the tag, each a link to its form.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;My schemas in the Library are editable: &lt;em&gt;Edit&lt;/em&gt; opens one in the schema editor and the code view, and
every change is kept in the library at once, with nothing to save.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The Flow tab shows only while the current file is an AsyncAPI spec.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A panel under the form and the right pane, as in VS Code, with a Problems tab: every finding of the
folder by file, with its rule and line, a filter, and a click that goes to the node. The status bar’s
error and warning counts show and hide it, and its height is resizable. The tree and the file list no
longer show problem counts.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The theme switch in the toolbar is one icon button that steps through the system’s palette, light and
dark.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The app icon is the website’s favicon, the genie over the word API, in the desktop shell and as the web
editor’s favicon.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restyled forms: sections with headings, short fields side by side, Write and Preview tabs opening into
the description’s bordered text box, quiet add and remove buttons, aligned table rows, tags and servers as pill toggles,
and the operation’s method badge. The schema editor draws guide lines from each schema to its
properties and branches, and its Details panel puts paired keywords side by side.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Splitters between the panes: drag the borders between the side bar, the form and the right pane,
and between the outline, the files and the Library, to resize them. Arrow keys move a focused
splitter, a double-click or Enter puts its pane back to the default size, and the sizes are kept
for the next visit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A menu bar: File (New…, Open Folder…, Open File…, Save, Save As…, Exit) and Edit (Undo, Redo), with
their shortcuts; on macOS, About and Quit are in the application menu and Edit has Cut, Copy, Paste
and Select All. New… starts an OpenAPI 3.1 or AsyncAPI 3.0 spec in the open folder; Open File…
opens the file’s folder with the file selected; Save As… writes the current file anywhere on disk.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Closing the window, quitting, or opening another folder with unsaved files asks whether to save
them first.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The web editor at &lt;a href=&quot;https://api-genie.dev/editor/&quot;&gt;https://api-genie.dev/editor/&lt;/a&gt;, deployed with the website: the same bundle as the
desktop shell’s, with the repository’s WebAssembly modules. The status bar and About show the commit
the editor was built from.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;About, in the toolbar: the editor’s version, the app’s, and where to read what each host offers
(the website’s “The editor’s hosts” page).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The app opens a folder given on its command line (&lt;code&gt;apigenie-editor &amp;lt;folder&amp;gt;&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The desktop shell: the editor in its own window on macOS, Windows and Linux, opening folders in
the native dialog and saving to them in place.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Try it for AsyncAPI operations: publish a message, with its payload and headers checked against
the message’s schemas first, or subscribe and watch what arrives, on the operation’s Kafka, AMQP,
MQTT or WebSocket servers. Needs Node.js 20 or later on the machine.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A mock server for OpenAPI specs, started from the toolbar: &lt;code&gt;apigenie-server&lt;/code&gt; serves the spec as it
is in the editor, saved or not, on this computer, and answers and validates requests as it does on
the command line. Try it out in the preview can send to it, and its log shows each request and what
didn’t match the spec. Needs API Genie 0.11.0 or later installed
(&lt;code&gt;npm install -g @mykulyak/api-genie&lt;/code&gt; or &lt;code&gt;brew install mykulyak/apigenie/apigenie&lt;/code&gt;), or
&lt;code&gt;APIGENIE_SERVER&lt;/code&gt; set to the &lt;code&gt;apigenie-server&lt;/code&gt; binary.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item></channel></rss>