svelte/test/validator/samples/properties-computed-must-be.../errors.json

[{
	"message": "Computed property name 'hours-hyphen' is invalid — must be a valid identifier such as hours_hyphen",
	"loc": {
		"line": 14,
		"column": 3
	},
	"pos": 150
}]
[1083] Svelte should throw a compile time error when illegal characters are used in computed names Approach: For each property name, construct a string that defines a function and see if parsing that string with Acorn throws an exception. If it does, assemble an informative error message that states which property is invalid, the first invalid character, and the location of that character within the name. Changes to codebase: - Added new validator test "properties-computed-must-be-valid-function-names" - Added new check into src/validate/js/propValidators/computed.ts, "checkForValidIdentifiers" - this check was added to src/validate/js/utils/checkForValidIdentifiers.ts like the other checks in "computed.ts" 7 years ago			`[{`
fix expected error position, tweak expected message to include suggested alternative 7 years ago			`"message": "Computed property name 'hours-hyphen' is invalid — must be a valid identifier such as hours_hyphen",`
[1083] Svelte should throw a compile time error when illegal characters are used in computed names Approach: For each property name, construct a string that defines a function and see if parsing that string with Acorn throws an exception. If it does, assemble an informative error message that states which property is invalid, the first invalid character, and the location of that character within the name. Changes to codebase: - Added new validator test "properties-computed-must-be-valid-function-names" - Added new check into src/validate/js/propValidators/computed.ts, "checkForValidIdentifiers" - this check was added to src/validate/js/utils/checkForValidIdentifiers.ts like the other checks in "computed.ts" 7 years ago			`"loc": {`
			`"line": 14,`
fix expected error position, tweak expected message to include suggested alternative 7 years ago			`"column": 3`
[1083] Svelte should throw a compile time error when illegal characters are used in computed names Approach: For each property name, construct a string that defines a function and see if parsing that string with Acorn throws an exception. If it does, assemble an informative error message that states which property is invalid, the first invalid character, and the location of that character within the name. Changes to codebase: - Added new validator test "properties-computed-must-be-valid-function-names" - Added new check into src/validate/js/propValidators/computed.ts, "checkForValidIdentifiers" - this check was added to src/validate/js/utils/checkForValidIdentifiers.ts like the other checks in "computed.ts" 7 years ago			`},`
fix expected error position, tweak expected message to include suggested alternative 7 years ago			`"pos": 150`
[1083] Svelte should throw a compile time error when illegal characters are used in computed names Approach: For each property name, construct a string that defines a function and see if parsing that string with Acorn throws an exception. If it does, assemble an informative error message that states which property is invalid, the first invalid character, and the location of that character within the name. Changes to codebase: - Added new validator test "properties-computed-must-be-valid-function-names" - Added new check into src/validate/js/propValidators/computed.ts, "checkForValidIdentifiers" - this check was added to src/validate/js/utils/checkForValidIdentifiers.ts like the other checks in "computed.ts" 7 years ago			`}]`