Lines Matching refs:features
206 '*features': FEATURES }
210 '*features': FEATURES }
243 The optional 'features' member specifies features. See Features_
272 '*features': FEATURES }
277 '*features': FEATURES }
319 The optional 'features' member specifies features. See Features_
333 '*features': FEATURES }
388 The optional 'features' member specifies features. See Features_
400 '*features': FEATURES }
444 The optional 'features' member specifies features. See Features_
467 '*features': FEATURES }
624 The optional 'features' member specifies features. See Features_
641 '*features': FEATURES }
674 The optional 'features' member specifies features. See Features_
694 For this purpose, a list of features can be specified for definitions,
706 'features': [ 'allow-negative-numbers' ] }
715 Special features
835 Likewise, features can be conditional. This requires the longhand
842 'features': [ { 'name': 'allow-negative-numbers',
1165 "features", and additional variant members depending on the value of
1179 Optional member "features" exposes the entity's feature strings as a
1234 name), "type" (the name of its type), "features" (a JSON array of
1250 "features" exposes the command's feature strings as a JSON array of
1258 "features": ["allow-negative-numbers"] }
1313 optionally "features" (a JSON array of feature strings). The