c28935b4e8
- Move the original guides for creating endpoints and middlewares to sub-sections in the Endpoints category. - Replace existing guides for endpoints and middlewares with the new approach. - Update all endpoints-related snippets across docs to use this new approach.
28 lines
1.3 KiB
Plaintext
28 lines
1.3 KiB
Plaintext
---
|
||
description: "Learn what feature flags in Medusa. Feature flags are used in Medusa to guard beta features that aren’t ready for live and production applications."
|
||
---
|
||
|
||
import DocCard from '@theme/DocCard';
|
||
import Icons from '@theme/Icon';
|
||
|
||
# Feature Flags
|
||
|
||
In this document, you’ll learn what feature flags in Medusa.
|
||
|
||
## Introduction
|
||
|
||
Feature flags are used in Medusa to guard beta features that aren’t ready for live and production applications. This allows the Medusa team to keep publishing releases more frequently, while also working on necessary future features behind the scenes. To use these beta features, you must enable their feature flags.
|
||
|
||
If a feature is guarded by a flag, entities, migrations, API Routes, and other resources associated with that feature are guarded by that flag as well. So, these resources will only be available to use in Medusa if you have enabled the associated feature flag.
|
||
|
||
You can view a list of available feature flags that you can toggle in [the Beta Features documentation](../../beta.md).
|
||
|
||
<DocCard item={{
|
||
type: 'link',
|
||
href: '/development/feature-flags/toggle',
|
||
label: 'Toggle Feature Flags',
|
||
customProps: {
|
||
icon: Icons['academic-cap-solid'],
|
||
description: 'Learn how to enable or disabled a feature flag.'
|
||
}
|
||
}} /> |