Refactor: Both warnings are dispatched inside `handleSelectChange` — i.e. as soon as the user picks **HELM** from the format dropdown, before any Save action. A user who selects HELM, sees the toast, then cancels the dialog (or switches to another format) has been warned about an export that never happens. The PR description also says the warning is "dispatched on HELM export", which doesn't match the actual call site.

[AlexeyGirin]

Both warnings are dispatched inside handleSelectChange — i.e. as soon as the user picks HELM from the format dropdown, before any Save action. A user who selects HELM, sees the toast, then cancels the dialog (or switches to another format) has been warned about an export that never happens. The PR description also says the warning is "dispatched on HELM export", which doesn't match the actual call site.

Consider moving the dispatch into handleSave (gated by currentFileFormat === 'helm') so it only fires when the user commits to exporting.

Also: the message "The molecule will be exported … appear as a CHEM monomer" is singular, but molecules.length can be > 1. Suggest pluralizing, e.g. "Molecules will be exported using inline SMILES, and on load will appear as CHEM monomers."

Originally posted by @claude[bot] in #10140 (comment)

[sabaPailodze]

Warning timing: The dispatch is intentionally in handleSelectChange, matching the existing isHelmCompatible warning that already fires on format selection — both fire together. The ticket's expected behavior and QA screenshots also show the toasts appearing while the Save dialog is open, before clicking Save. Moving it to handleSave would delay the toast until after the dialog closes and break the documented behavior. (The PR description's "on export" wording was imprecise — a doc nit, not a code issue.)

Pluralization: The message string is prescribed verbatim by the ticket (per @ljubica-milovic's request + screenshot): The molecule will be exported using inline SMILES, and on load will appear as a CHEM monomer. Changing the wording would deviate from the agreed spec and what QA validates against.

The current implementation matches the requirements, so closing this.