0.2.4

The settings tab has its input fields back

0.2.3 shipped a settings tab that rendered no input controls on Obsidian
1.13 or later: every setting appeared as a name and a description with nothing
to type into. Legible, and completely inert. If you are on 1.13+, upgrade —
there is no workaround short of editing data.json by hand.

Fixes #5

What happened

Obsidian 1.13 renders a settings tab from getSettingDefinitions() and stops
calling display() as soon as that array comes back non-empty. 0.2.3 added
getSettingDefinitions() to feed the new settings search with names and
descriptions only, on the assumption that display() would carry on rendering
— so all 37 rows arrived without their controls. Below 1.13 the API does not
exist, display() still ran, and the tab worked, which is why it passed
testing against minAppVersion 1.7.2 and shipped broken to everyone above it.

Introduced in https://github.com/kaimys/obsidian-dispatch/releases/tag/0.2.3 —
that release note claimed rendering was unchanged on 1.13+. It was not, and
this is the correction.

No settings were lost. data.json and the device-local config kept their
values and the board kept reading them throughout; only editing from the UI was
affected.

The trade-off

Dispatch is invisible to Obsidian's 1.13+ settings search again, which is the
feature 0.2.3 was reaching for. Keeping it would mean porting all 37 settings
to declarative control/render definitions and raising minAppVersion
to 1.13, dropping every user below it. That is a deliberate decision rather
than a lint fix, and it is not scheduled.

minAppVersion stays at 1.7.2. Nothing else changes: no migration, no
configuration change, no behaviour change outside the settings tab.

Install

Download main.js, manifest.json and styles.css below into
<vault>/.obsidian/plugins/dispatch/, or install Dispatch from Obsidian's
community plugin directory. Requires Obsidian 1.7.2+. Desktop only.

Full changelog: 0.2.3...0.2.4