{"version":"2.1.267","anchor":"bug-fix-availablemodels-validator-was-reading-from-the-wron","canonical_anchor":"bug-fix-availablemodels-validator-was-reading-from-the-wron","heading":"Bug fix: availableModels validator was reading from the wrong variables","tier":"notice","area":"Model Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/bug-fix-availablemodels-validator-was-reading-from-the-wron","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Bug fix: availableModels validator was reading from the wrong variables\n\nFixed a bug where the availableModels setting validator checked the wrong internal variables\n\n**What**\n\nThe validation logic for the `availableModels` setting, which restricts which models people can pick, had a bug: it was reading from and writing to internal variables that didn't match its own inputs, so it wasn't actually validating the list it was given. This has been fixed so it correctly checks the input array and only keeps valid string entries.\n\n**Why**\n\nThis fixes a case where `availableModels` validation could behave incorrectly, for example failing to catch or properly report a non-string entry in the list. Anyone using this setting to restrict model selection should see it validated correctly now.\n\n- Area: Model Settings\n- Names: `availableModels`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}