Skip to content

Commit ec1f092

Browse files
committed
fix: docs
1 parent c03fb02 commit ec1f092

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,7 @@ Each feature flag can have a list of conditions that must be met for the feature
193193

194194
To get started, add a `#### Conditions` subheading to the feature issue and list the conditions as a series of checkboxes. If all conditions are met, the feature will be enabled. If a condition checkbox is unchecked, it will be ignored during evaluation. In other words, if a condition checkbox is not checked, it will not affect the feature flag.
195195

196-
````markdown
196+
```markdown
197197
# 🏁 Feature Flags
198198

199199
## My feature
@@ -213,8 +213,7 @@ Now define how the condition is evaluated during runtime.
213213

214214
The `requestToContext` is a good place to extract information from the request object that is needed to evaluate the conditions. For example, you can extract cookies or headers from the request object to determine if a user is signed in.
215215

216-
> ‼️ Important: The `requestToContext` function is only called when communicating with the `NextFlag` API over HTTP. If you are using the `NextFlag` directly in a server-side component, you must build the context object yourself and pass it to the `isFeatureEnabled` method directly.
217-
```
216+
>❗ Important: The `requestToContext` function is only called when communicating with the `NextFlag` API over HTTP. If you are using the `NextFlag` directly in a server-side component, you must build the context object yourself and pass it to the `isFeatureEnabled` method directly.
218217
219218
```ts
220219
// src/app/api/next-flag/index.ts

0 commit comments

Comments
 (0)