{"version":"2.1.321","anchor":"bridge-fast-path-now-honours-settings","canonical_anchor":"bridge-fast-path-now-honours-settings","heading":"The bridge command now applies --settings","tier":"use","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bridge-fast-path-now-honours-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### The bridge command now applies `--settings`\n\nStarting the bridge command with `--settings` now loads that settings file, which the command used to ignore\n\n**What**\n\nThe bridge command now reads the `--settings` option and applies it before it continues. `--settings` takes a path to a settings JSON file, or a JSON string typed directly. Its values override the same keys in your `settings.json` files. Before, the bridge command ignored this option.\n\n**Why**\n\nSettings you pass to the bridge command now take effect.\n\n- Area: Remote Control\n- Names: `--settings`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}