You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change causes the "env" setting to require
that its JSON value is a mapping from strings to
strings, or int for legacy compatibility; but other
values (float, array, object, null, bool) are now
rejected.
Also, group all the deprecated settings together with
a comment to resist the temptation to delete them.
Change-Id: I7eb2f017e9cda4a3821370034b8e95809a3d8e11
Reviewed-on: https://go-review.googlesource.com/c/tools/+/593075
LUCI-TryBot-Result: Go LUCI <[email protected]>
Reviewed-by: Robert Findley <[email protected]>
returnsoftErrorf("gopls setting \"allowImplicitNetworkAccess\" is deprecated.\nPlease comment on https://go.dev/issue/66861 if this impacts your workflow.")
1080
1061
1081
-
case"experimentalUseInvalidMetadata":
1082
-
returndeprecatedError("")
1083
-
1084
1062
case"standaloneTags":
1085
1063
returnsetStringSlice(&o.StandaloneTags, value)
1086
1064
1087
-
case"allExperiments":
1088
-
// golang/go#65548: this setting is a no-op, but we fail don't report it as
1089
-
// deprecated, since the nightly VS Code injects it.
1090
-
//
1091
-
// If, in the future, VS Code stops injecting this, we could theoretically
1092
-
// report an error here, but it also seems harmless to keep ignoring this
1093
-
// setting forever.
1094
-
1095
-
case"newDiff":
1096
-
returndeprecatedError("")
1097
-
1098
1065
case"subdirWatchPatterns":
1099
1066
returnsetEnum(&o.SubdirWatchPatterns, value,
1100
1067
SubdirWatchPatternsOn,
@@ -1116,7 +1083,13 @@ func (o *Options) set(name string, value any, seen map[string]struct{}) error {
1116
1083
case"zeroConfig":
1117
1084
returnsetBool(&o.ZeroConfig, value)
1118
1085
1119
-
// Replaced settings.
1086
+
// deprecated and renamed settings
1087
+
//
1088
+
// These should never be deleted: there is essentially no cost
1089
+
// to providing a better error message indefinitely; it's not
1090
+
// as if we would ever want to recycle the name of a setting.
1091
+
1092
+
// renamed
1120
1093
case"experimentalDisabledAnalyses":
1121
1094
returndeprecatedError("analyses")
1122
1095
@@ -1138,7 +1111,45 @@ func (o *Options) set(name string, value any, seen map[string]struct{}) error {
1138
1111
case"caseSensitiveCompletion":
1139
1112
returndeprecatedError("matcher")
1140
1113
1141
-
// Deprecated settings.
1114
+
case"experimentalDiagnosticsDelay":
1115
+
returndeprecatedError("diagnosticsDelay")
1116
+
1117
+
// deprecated
1118
+
case"memoryMode":
1119
+
returndeprecatedError("")
1120
+
1121
+
case"tempModFile":
1122
+
returndeprecatedError("")
1123
+
1124
+
case"experimentalWorkspaceModule":
1125
+
returndeprecatedError("")
1126
+
1127
+
case"experimentalTemplateSupport":
1128
+
returndeprecatedError("")
1129
+
1130
+
case"experimentalWatchedFileDelay":
1131
+
returndeprecatedError("")
1132
+
1133
+
case"experimentalPackageCacheKey":
1134
+
returndeprecatedError("")
1135
+
1136
+
case"allowModfileModifications":
1137
+
returndeprecatedError("")
1138
+
1139
+
case"allExperiments":
1140
+
// golang/go#65548: this setting is a no-op, but we fail don't report it as
1141
+
// deprecated, since the nightly VS Code injects it.
1142
+
//
1143
+
// If, in the future, VS Code stops injecting this, we could theoretically
1144
+
// report an error here, but it also seems harmless to keep ignoring this
0 commit comments