<commit_before>eslint-extjs
============
[![NPM version](https://badge.fury.io/js/eslint-plugin-extjs.png)](http://badge.fury.io/js/eslint-plugin-extjs)

ESLint rules for projects using the ExtJS framework.

## Rule Details

### ext-array-foreach

The two main array iterator functions provided by ExtJS, [`Ext.Array.forEach`][ext-array-foreach]
and [`Ext.Array.each`][ext-array-each], differ in that `each` provides extra
functionality for early termination and reverse iteration. The `forEach` method,
however, will delegate to the browser's native [`Array.forEach`][array-foreach]
implementation where available, for performance. So, in situations where the
extra features of `each` are not needed, `forEach` should be preferred. As the
`forEach` documentation says:

> [Ext.Array.forEach] will simply delegate to the native Array.prototype.forEach
> method if supported. It doesn't support stopping the iteration by returning
> false in the callback function like each. However, performance could be much
> better in modern browsers comparing with each.

The following patterns are considered warnings:<commit_msg>Rename to match package and add version notice.<commit_after>eslint-plugin-extjs
============
[![NPM version](https://badge.fury.io/js/eslint-plugin-extjs.png)](http://badge.fury.io/js/eslint-plugin-extjs)

ESLint rules for projects using the ExtJS framework. These rules are targeted for use with ExtJS 4.x. Pull requests for compatibility with 5.x are welcome!

## Rule Details

### ext-array-foreach

The two main array iterator functions provided by ExtJS, [`Ext.Array.forEach`][ext-array-foreach]
and [`Ext.Array.each`][ext-array-each], differ in that `each` provides extra
functionality for early termination and reverse iteration. The `forEach` method,
however, will delegate to the browser's native [`Array.forEach`][array-foreach]
implementation where available, for performance. So, in situations where the
extra features of `each` are not needed, `forEach` should be preferred. As the
`forEach` documentation says:

> [Ext.Array.forEach] will simply delegate to the native Array.prototype.forEach
> method if supported. It doesn't support stopping the iteration by returning
> false in the callback function like each. However, performance could be much
> better in modern browsers comparing with each.

The following patterns are considered warnings:
{'fraction_non_alphanumeric': 0.10168067226890756, 'fraction_numerical': 0.0008403361344537816, 'mean_word_length': 5.332446808510638, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2692167', 'n_tokens_mistral': 631, 'n_tokens_neox': 614, 'n_words': 263}