{"version":"2.1.273","anchor":"apply-flag-settings-control-response-strips-an-internal-key","canonical_anchor":"apply-flag-settings-control-response-strips-an-internal-key","heading":"apply_flag_settings control response strips an internal key","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/apply-flag-settings-control-response-strips-an-internal-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### apply_flag_settings control response strips an internal key\n\napply_flag_settings control response handler now explicitly strips one internal key before returning settings\n\n**Unclear.** What the stripped internal key represents or why it needed excluding is not stated.\n\n**What**\n\nThe handler that reads `apply_flag_settings` settings out of a control response was rewritten. It now explicitly pulls out one specific internal key and returns the rest, instead of the previous approach of rebuilding the settings object generically from `setting`\/`name` pairs.\n\n**Why**\n\nThis is an internal implementation change to how flag settings are extracted from a control response; the finding doesn't indicate a user-facing effect.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}