{"version":"2.1.246","anchor":"plugin-hooks-can-ask-for-feature-flag-values-but-the-answer-","canonical_anchor":"plugin-hooks-can-ask-for-feature-flag-values-but-the-answer-","heading":"Plugin hooks can ask for feature flag values, but the answer is always false","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/plugin-hooks-can-ask-for-feature-flag-values-but-the-answer-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Plugin hooks can ask for feature flag values, but the answer is always false\n\nPlugin hooks can ask for feature flag values but every answer comes back false.\n\n**What**\n\nPlugin hook engines gain a `flag` object with a `value(name, fallback)` call, backed by a new host operation `flag.value` that is listed unconditionally in the plugin operation table. The implementation shipped alongside it returns false, so nothing a plugin asks for comes back true in this build.\n\n**Details**\n\n- The `flag` object is sealed; plugins cannot add to or replace it.\n- Neither the operation nor the object exists in the previous release.\n\n**Evidence**\n\n`flag.value`\n\n- Area: Plugins\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}