7 Commits (c29dc42e2ede0ff2b23435b9fb8c577ea02306ce)

Author	SHA1	Message	Date
Rich Harris	5a457bfb87	rename loc to start, include character info in locations	7 years ago
Rich Harris	39ad124c99	update validation tests	7 years ago
Rich Harris	b86a1edb52	add codes to validation errors	7 years ago
James Birtles	da6a74016f	add end position to errors	7 years ago
Rich Harris	b19303679d	simplify test slightly, add test for reserved words	7 years ago
Rich Harris	146327e87f	fix expected error position, tweak expected message to include suggested alternative	7 years ago
asweingarten	02afdb03fa	[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