Chaning "read-write" to "writable" in error messages

This commit is contained in:
Anders Hejlsberg
2016-01-19 09:45:46 -08:00
parent a499607845
commit dc8ab95db5
2 changed files with 5 additions and 5 deletions
+3 -3
View File
@@ -5641,7 +5641,7 @@ namespace ts {
}
if (isReadonlySymbol(sourceProp) && !isReadonlySymbol(targetProp)) {
if (reportErrors) {
reportError(Diagnostics.Property_0_is_read_only_in_type_1_but_read_write_in_type_2,
reportError(Diagnostics.Property_0_is_read_only_in_type_1_but_writable_in_type_2,
symbolToString(targetProp), typeToString(source), typeToString(target));
}
return Ternary.False;
@@ -5780,7 +5780,7 @@ namespace ts {
}
if (sourceInfo.isReadonly && !targetInfo.isReadonly) {
if (reportErrors) {
reportError(Diagnostics.Index_signature_is_read_only_in_type_0_but_read_write_in_type_1,
reportError(Diagnostics.Index_signature_is_read_only_in_type_0_but_writable_in_type_1,
typeToString(source), typeToString(target));
}
return Ternary.False;
@@ -5826,7 +5826,7 @@ namespace ts {
}
if ((sourceStringInfo && sourceStringInfo.isReadonly || sourceNumberInfo && sourceNumberInfo.isReadonly) && !targetInfo.isReadonly) {
if (reportErrors) {
reportError(Diagnostics.Index_signature_is_read_only_in_type_0_but_read_write_in_type_1,
reportError(Diagnostics.Index_signature_is_read_only_in_type_0_but_writable_in_type_1,
typeToString(source), typeToString(target));
}
return Ternary.False;
+2 -2
View File
@@ -995,7 +995,7 @@
"category": "Error",
"code": 2342
},
"Property '{0}' is read-only in type '{1}' but read-write in type '{2}'.": {
"Property '{0}' is read-only in type '{1}' but writable in type '{2}'.": {
"category": "Error",
"code": 2343
},
@@ -1087,7 +1087,7 @@
"category": "Error",
"code": 2365
},
"Index signature is read-only in type '{0}' but read-write in type '{1}'.": {
"Index signature is read-only in type '{0}' but writable in type '{1}'.": {
"category": "Error",
"code": 2366
},