From 1fe991a00dde60c91111f18da95c71b7e208f264 Mon Sep 17 00:00:00 2001 From: Leo Balter Date: Mon, 8 May 2017 16:05:13 -0400 Subject: [PATCH] Add minimal documentation for features flags (#1022) --- FEATURES.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 FEATURES.md diff --git a/FEATURES.md b/FEATURES.md new file mode 100644 index 0000000000..78d4e6694f --- /dev/null +++ b/FEATURES.md @@ -0,0 +1,16 @@ +# Feature Flags + +Current, post-ES2015, flags used to identify new features: + +- `async-functions`: Async Functions +- `async-iteration`: [Async Iteration and Generators](https://github.com/tc39/proposal-async-iteration) +- `object-rest`: [Object rest/spread properties](https://github.com/tc39/proposal-object-rest-spread) +- `object-spread`: [Object rest/spread properties](https://github.com/tc39/proposal-object-rest-spread) +- `regexp-dotall`: [RegExp s (dotAll) flag](https://github.com/tc39/proposal-regexp-dotall-flag) +- `regexp-lookbehind`: [RegExp lookBehind](https://github.com/tc39/proposal-regexp-lookbehind) +- `regexp-named-groups`: [RegExp named groups capturing]() +- `regexp-unicode-property-escapes`: [RegExp Unicode Property Escapes](https://github.com/tc39/proposal-regexp-unicode-property-escapes) +- `SharedArrayBuffer` +- `Symbol.asyncIterator` + +While it's mostly optional when already in a current released specification, it's highly recommended to reuse the features flags for any matching case in new tests.