{"version":"2.1.223","anchor":"invalid-config-dialog-is-now-awaited-before-returning","canonical_anchor":"invalid-config-dialog-is-now-awaited-before-returning","heading":"Invalid config dialog is now awaited before returning","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/invalid-config-dialog-is-now-awaited-before-returning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Invalid config dialog is now awaited before returning\n\nA broken config file now holds the startup dialog until you dismiss it instead of racing past.\n\n**What**\n\nWhen a configuration file fails to parse at startup, the process waits for the dialog to be dismissed instead of continuing past it.\n\n**Details**\n\n- The startup handler previously returned the dialog promise directly; it now awaits `showInvalidConfigDialog` and then returns.\n- The non-interactive path is unchanged: it writes \"Configuration error in \" to stderr and exits 1.\n\n**Evidence**\n\n`Configuration error in `\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}