test262/tools/lint/test/fixtures/features.txt

# Here is a full-line comment: not-a-valid-feature
async-functions  # This is a partial-line comment
object-spread
generators
BigInt
TypedArray
linter: Fix parsing features.txt Previously, split() would split on whitespace, then the if-condition would remove `#` - interpreting every word in every comment in the file as a potential valid feature flag. We want splitlines() here. Partial-line comments were inadvertently "supported" before, because of this bug. Instead, support them explicitly by chopping off a `#` character, anything after it, and any whitespace immediately preceding it. 2023-02-13 21:40:21 +01:00			`# Here is a full-line comment: not-a-valid-feature`
			`async-functions # This is a partial-line comment`
lint: Increase isolation between tests and project Prior to this commit, the tests for the linter partially depended on project files. This coupling risks churn in the tests: if the needs of the project change (e.g. a harness file is modified), then the linter tests would need to be updated. It also made the tests more difficult to understand because the input was both larger and more complicated than necessary to exercise the relevant functionality. Execute the tests in the context of the fixture directory and introduce minimal support files that serve the same purpose as the corresponding project files. 2019-09-25 18:01:27 +02:00			`object-spread`
			`generators`
			`BigInt`
			`TypedArray`