From 1c695394cb65c389797dcbd7738933e17d3150f6 Mon Sep 17 00:00:00 2001 From: maliming Date: Wed, 13 Nov 2019 15:27:28 +0800 Subject: [PATCH] Update Settings.md --- docs/en/Settings.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/Settings.md b/docs/en/Settings.md index c9b3e9b64e..5a5616a71a 100644 --- a/docs/en/Settings.md +++ b/docs/en/Settings.md @@ -145,6 +145,7 @@ public class CustomSettingValueProvider : SettingValueProvider Every provider should have a unique Name (which is "Custom" here). Built-in providers use the given names: * `DefaultValueSettingValueProvider`: "**D**". +* `ConfigurationSettingValueProvider`: "**C**". * `GlobalSettingValueProvider`: "**G**". * `TenantSettingValueProvider`: "**T**". * `UserSettingValueProvider`: "**U**". @@ -176,4 +177,4 @@ You can replace this service in the dependency injection system to customize the The core setting system is pretty independent and doesn't make any assumption about how you manage (change) the setting values. Even the default `ISettingStore` implementation is the `NullSettingStore` which returns null for all setting values. -The setting management module completes it (and implements `ISettingStore`) by managing setting values in a database. See the [Setting Management Module document](Modules/Setting-Management.md) for more. \ No newline at end of file +The setting management module completes it (and implements `ISettingStore`) by managing setting values in a database. See the [Setting Management Module document](Modules/Setting-Management.md) for more.