paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 38 Packages Projects Releases Wiki Activity

fix: update more /docs/references links

Browse Source 
Signed-off-by: aramissennyeydd <aramis.sennyey@doordash.com>
This commit is contained in:
aramissennyeydd
2026-02-04 10:11:36 -06:00
parent f2fc1def80
commit efbf232bfa
40 changed files with 95 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins/feature-flags.md
+2 -2
View File
@@ -55,7 +55,7 @@ The user's selection is saved in the user's browser local storage. Once a featur
## FeatureFlagged Component
The easiest way to control content based on the state of a feature flag is to use the [FeatureFlagged](https://backstage.io/docs/reference/core-app-api.featureflagged) component.
The easiest way to control content based on the state of a feature flag is to use the [FeatureFlagged](https://backstage.io/api/stable/functions/_backstage_core-app-api.FeatureFlagged.html) component.
```ts
import { FeatureFlagged } from '@backstage/core-app-api';
@@ -73,7 +73,7 @@ import { FeatureFlagged } from '@backstage/core-app-api';
## Evaluating Feature Flag State
It is also possible to query a feature flag using the [FeatureFlags Api](https://backstage.io/docs/reference/core-plugin-api.featureflagsapi).
It is also possible to query a feature flag using the [FeatureFlags Api](https://backstage.io/api/stable/interfaces/_backstage_core-plugin-api.index.FeatureFlagsApi.html).
```ts
import { useApi, featureFlagsApiRef } from '@backstage/core-plugin-api';