QuickAdd 2.32.1

A bug-fix release. In the one-page form, a note picker's suggestions now open below the field instead of covering the form title. A user script that does its work without exporting anything no longer stops its macro with an error. And three fixes for apps that name a run's current note with current=.

To update, open Settings → Community plugins, click Check for updates, and then Update next to QuickAdd.

Suggestions open below the field in the one-page form

In the one-page form, a note picker's suggestion list could open upward and cover the form's title, the File name preview, and the fields above it, even when there was room below. Since 2.29.0, a prompt's list flipped above the field whenever the whole list would reach the Submit bar, and a shorter list below was never tried. In the form below, the empty Who did you talk to? field's list covered the title and the Which client? field:

Before	After

Now the list stays below the field, shortened and scrollable, whenever at least 150 px fit between the field and the Submit bar. With less room than that, it opens on the roomier side. The last field's list still opens above so that Submit stays clickable. Text prompts that come one at a time follow the same rule. Pickers in the settings pages are unchanged (#2206, #2212).

A user script that exports nothing finishes its macro

A user script that does all its work at the top level, such as one that creates a folder and exports no function, ran fine, and then QuickAdd said the script "is an empty object", showed an error notice, and stopped the macro. Later steps never ran. Now such a script finishes with no output and the macro continues.

One thing to know: a script that defines a function but forgets to export it now does nothing and shows no error, where before it showed this one. QuickAdd can't tell that case apart from a script that means to run at the top level. A Script::member that points at an empty object still raises the error.

Thanks to @RumiaKitinari for #2208 (#2209).

For apps that drive QuickAdd

Three follow-ups to the current= option from 2.32.0:

• A clearer error with current=none. A choice that needs the current note, such as Capture to active file, a strict Link to captured file, or a {{LINKCURRENT}}, now fails with This choice needs a current note, and the run was started with current=none. Before, it told the caller to open a file in the editor, which a run started from outside Obsidian can't do. In-app runs with no file open keep the message they had.
• The named note applies only to its run. A macro script that keeps params.quickAddApi and runs a choice later now reads the active tab again, as before. The note given with current= no longer stays pinned on that executor.
• An Obsidian Command step uses the named note. A macro step that runs another QuickAdd choice through its command, such as QuickAdd: Add to inbox, now gets the macro's named note, the way a Choice step already did. Before, that step read the active tab.

Docs: current= (#2203, #2204, #2205, #2211).

Also in this release

Fixes

• Choice commands after a disable or reload. When data.json changed on disk, for example through Sync, in the same moment QuickAdd was disabled or reloaded, the old plugin instance could still add its choice commands to the command palette after it had unloaded. After a disable, the commands stayed in the palette. After a reload, running a choice command could go to the old, unloaded instance, so the run didn't see the current note or the choice chain the macro had handed it. An unloaded QuickAdd now adds and removes no commands (#2210, #2215).

Full changelog: 2.32.0...2.32.1