Feature Flag Determination

๐Ÿ“˜

Feature flags are only available for SDK version 2.0.0 or higher.

When using feature flags, please apply SDK version 2.0.0 or higher when adding dependencies.

A feature flag has an on and off state. You will set different features according to each state.

Once a feature flag is applied, a specific user from your traffic should be able to either receive an on or off status. This on/off status determination can be done through the Hackle SDK.

useFeature

You can use the Hooks API provided by Hackle to receive status results for the user. At this time, you need to pass the feature key, and then implement the logic according to each on/off status.

In the example code below, we are passing feature key 42.

function App() {
  return (
    // Determines the status of the feature flag to assign the user in a feature flag with a feature key of 42.
    // For undetermined cases, users are assigned to false (off status). 
    <Feature featureKey={42}>
      {(featureOn) =>
        featureOn ? (
          <SuperAwesomeFeature /> // Logic for on status
        ) : (
          <AwesomeFeature /> // Logic for off status
        )
      }
    </Feature>
  )
}
function App() {
  // ๊ธฐ๋Šฅ ํ‚ค๊ฐ€ 42์ธ ๊ธฐ๋Šฅ ํ”Œ๋ž˜๊ทธ์—์„œ ์‚ฌ์šฉ์ž์˜ ์ƒํƒœ๋ฅผ ๊ฒฐ์ •ํ•ฉ๋‹ˆ๋‹ค.
  // ๊ฒฐ์ •ํ•˜์ง€ ๋ชปํ•˜๋Š” ์ƒํ™ฉ์ธ ๊ฒฝ์šฐ false(๊บผ์ง ์ƒํƒœ)๋ฅผ ๋ฐ˜ํ™˜ํ•ฉ๋‹ˆ๋‹ค.
  const featureOn = useFeature(42)
  return (
    <>
    {
      featureOn ? (
        <SuperAwesomeFeature /> // ์ผœ์ง ์ƒํƒœ์ผ ๋•Œ์˜ ๊ธฐ๋Šฅ
      ) : (
        <AwesomeFeature /> // ๊บผ์ง ์ƒํƒœ์ผ ๋•Œ์˜ ๊ธฐ๋Šฅ
      )
    }
    </>
  )
}

useFeatureFlagDetail

The useFeatureFlagDetail() Hooks API works the same as useFeature() but additionally provides a reason for the determination of a status for a particular user. This can be useful when you want to check whether the manual allocation is working well or when you think that the traffic allocation you have set is not being reflected in your results.

You must pass a function key as a parameter. For the example code below, we are passing function key 42.

// Status determination details
const decision = useFeatureFlagDetail(42)

// Feature flag on/off results 
const isOn = decision.isOn

// Reason for status determination
const reason = decision.reason

The reason for the status determination will be in the form of SDK_NOT_READY. Please refer to the table below for the full list of all the different types of reasons.

Reason

Description

Feature Status

SDK_NOT_READY

The SDK is not ready to use.
(e.g. trying to initialize with the wrong SDK key)

Default status(off)

FEATURE_FLAG_NOT_FOUND

No feature flags were found for the function key you passed in.
The feature key may be incorrect or the corresponding feature flag may be in an archived state.

Default status(off)

FEATURE_FLAG_INACTIVE

The feature flag is off.

Default status(off)

INDIVIDUAL_TARGET_MATCH

User has been matched to individual targeting settings.

Set to individual targeting

TARGET_RULE_MATCH

User has been matched to audience targeting settings.

Set to audience targeting

DEFAULT_RULE

User has not been matched to either individual targeting or audience targeting.

Set to default status

INVALID_INPUT

The input value is not valid.
(Example: character type entered in a parameter that requires a numeric type)

Default status(off)

EXCEPTION

An unknown error has occurred.

Default status(off)


Did this page help you?