gregswindle / eslint-plugin-crc Goto Github PK

View Code? Open in Web Editor NEW

5.0 3.0 5.0 3.76 MB

Analyze, model, and refactor JavaScript codebases with auto-generated Class-Responsibility-Collaborator models.

License: MIT License

JavaScript 100.00%

refactoring refactor refactoring-tools javascript javascript-tools code-analysis cli reports ast crc

eslint-plugin-crc's People

Contributors

Stargazers

Watchers

Forkers

glavin001 fossabot gabssnake

eslint-plugin-crc's Issues

epic(reports): generate CRC Model reports

Epic summary

As a software product delivery stakeholder,
I want a simple portrayal of the software that models my domain
In order to communicate with a common vocabulary based on community goals.

Acceptance criteria

1. Reports in the form of CRC Models can be generated and shared.
2. CRC Model report generation can be automated and incorporated into CI/CD.

⚡ Rule developers must use the `eslint:rule` subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

Create a stubbed rule,

The rule's stubbed BDD specs,

As well as the rule's documentation.

See eslint-plugin development environment for details.

feat(collaborators): list objects, modules, and functions that an object uses

User story

As a developer/designer,
I need to see the full list of dependencies invoked within an object
In order to maintain a SOLID GRASP of my software.

Acceptance criteria

1. Every prototypical object invoked by an object appears as a "Collaborator."
2. Each Collaborator entry has an array of invocation ranges.

⚡ Rule developers must use the `eslint:rule` subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

Create a stubbed rule,

The rule's stubbed BDD specs,

As well as the rule's documentation.

See eslint-plugin development environment for details.

An in-range update of espree is breaking the build 🚨

Version 3.4.2 of espree just got published.

Branch	Build failing 🚨
Dependency	espree
Current Version	3.4.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

espree is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/gregswindle/eslint-plugin-crc/builds/224500165),- ❌ **bitHound - Dependencies** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fespree-3.4.2),- ❌ **bitHound - Code** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fespree-3.4.2),- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/197201)

Release Notes

v3.4.2

c99e436 Upgrade: eslint to 2.13.1 (#328) (Teddy Katz)
628cf3a Fix: don't mutate user-provided configs (fixes #329) (#330) (Teddy Katz)

Commits

The new version differs by 4 commits0.

b9140c3 3.4.2
5c9a692 Build: changelog update for 3.4.2
c99e436 Upgrade: eslint to 2.13.1 (#328)
628cf3a Fix: don't mutate user-provided configs (fixes #329) (#330)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.1.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Dependencies 5 failing dependencies. Details
❌ bitHound - Code 1 failing file. Details

Commits

The new version differs by 6 commits .

455619f chore(release): 10.2.0
95cc09a feat: upgrade to version of yargs with extend support (#541)
43535f9 chore: explicit update of istanbuljs dependencies (#535)
98ebdff feat: allow babel cache to be enabled (#517)
50adde4 feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834 chore(package): update tap to version 10.0.0 (#507)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Validate commit messages

Issue type

Enhancement/feature request

User story

As a contributor,
I need my commit messages validated
In order to ensure automated CHANGELOGs and release docs are properly generated.

Acceptance criterion

Commit messages that do not conform to the angular preset for conventional changelogs are rejected on pre-commit.

Possible Solutions

~~1. ghooks~~
~~2. validate-commit-msg~~
~~3. commitizen~~
~~4. angular-precommit~~

Context

This is necessary to enable automated CHANGELOG updates.

An in-range update of codecov is breaking the build 🚨

Version 2.2.0 of codecov just got published.

Branch	Build failing 🚨
Dependency	codecov
Current Version	2.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codecov is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ dependency-ci Failed dependency checks Details,- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ✅ bitHound - Dependencies No failing dependencies. Details,- ❌ bitHound - Code 1 failing file. Details

Release Notes

v2.2.0

Added: Support for Jenkins Blue Ocean
Added: Clear function to remove all discovered reports after uploading
Fix for Gitlab CI

Commits

The new version differs by 8 commits0.

7f8a29b v2.2.0
576b9fe add CI_REPOSITORY_URL to gitlab detection, fix #60
74a44f2 added -C to unlink reports after uploading
d1bf5e4 Merge pull request #56 from rochdev/blue-ocean
0a3cea3 Add support for Jenkins Blue Ocean
b365cd8 Merge pull request #57 from codecov/fix/cleanup
7f220cc Removing old execSync code from tests
4ba4609 v2.1.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Research Istanbul

Tasks

Read istanbul's source code and document:

- Which AST parser is used

Istanbul uses Esprima to generate ASTs.

- How istanbul detects coverage over multiple source code files
- What kind of tree elements are inspected the most

An in-range update of eslint is breaking the build 🚨

Version 3.19.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.18.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
✅ bitHound - Code No failing files. Details
❌ bitHound - Dependencies 5 failing dependencies. Details

Release Notes

v3.19.0

e09132f Fix: no-extra-parens false positive with exports and object literals (#8359) (Teddy Katz)
91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357) (Vitor Balocco)
35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349) (Teddy Katz)
3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358) (Teddy Katz)
f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371) (Teddy Katz)
02f0d27 Docs: Add soda0289 to Development Team (#8367) (Kai Cataldo)
155424c Fix: ignore empty path in patterns (fixes #8362) (#8364) (alberto)
27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297) (Vitor Balocco)
8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361) (Teddy Katz)
5878593 Chore: fix invalid syntax in no-param-reassign test (#8360) (Teddy Katz)
1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323) (Teddy Katz)
29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335) (Teddy Katz)
0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340) (Teddy Katz)
41b9786 Fix: no-extra-parens false positive with objects following arrows (#8339) (Teddy Katz)
3146167 Fix: eslint.verify should not mutate config argument (fixes #8329) (#8334) (alberto)
927de90 Fix: dot-notation autofix produces invalid syntax for integer properties (#8332) (Teddy Katz)
a9d1bea Fix: comma-style autofix produces errors on parenthesized elements (#8331) (Teddy Katz)
d52173f Fix: don't generate invalid options in config-rule (#8326) (Teddy Katz)
6eda3b5 Fix: no-extra-parens invalid autofix in for-of statements (#8337) (Teddy Katz)
6c819d8 Fix: dot-notation autofix produces errors on parenthesized computed keys (#8330) (Teddy Katz)
2d883d7 Fix: object-shorthand autofix produces errors on parenthesized functions (#8328) (Teddy Katz)
cd9b774 Fix: quotes false positive with backtick option in method names (#8327) (Teddy Katz)
d064ba2 Fix: no-else-return false positive for ifs in single-statement position (#8338) (Teddy Katz)
6a718ba Chore: enable max-statements-per-line on ESLint codebase (#8321) (Teddy Katz)
614b62e Chore: update sinon calls to deprecated API. (#8310) (alberto)
0491572 Chore: use precalculated counts in codeframe formatter (#8296) (Vitor Balocco)
8733e6a Chore: Fix incorrect error location properties in tests (#8307) (alberto)
c4ffb49 Chore: Fix typos in test option assertions (#8305) (Teddy Katz)
79a97cb Upgrade: devDependencies (#8303) (alberto)
e4da200 Upgrade: Mocha to 3.2.0 (#8299) (Ilya Volodin)
2f144ca Fix: operator-assignment autofix errors with parentheses (fixes #8293) (#8294) (Teddy Katz)
7521cd5 Chore: update token logic in rules to use ast-utils (#8288) (Teddy Katz)
9b509ce Chore: refactor space-before-function-paren rule (#8284) (Teddy Katz)
ddc6350 Fix: no-param-reassign false positive on destructuring (fixes #8279) (#8281) (Teddy Katz)
f8176b3 Chore: improve test coverage for node-event-generator (#8287) (Teddy Katz)
602e9c2 Docs: fix incorrect selector examples (#8278) (Teddy Katz)

Commits

The new version differs by 38 commits .

421aab4 3.19.0
26a4dd5 Build: changelog update for 3.19.0
e09132f Fix: no-extra-parens false positive with exports and object literals (#8359)
91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357)
35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349)
3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358)
f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371)
02f0d27 Docs: Add soda0289 to Development Team (#8367)
155424c Fix: ignore empty path in patterns (fixes #8362) (#8364)
27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297)
8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361)
5878593 Chore: fix invalid syntax in no-param-reassign test (#8360)
1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323)
29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335)
0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340)

There are 38 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

feat(reports): add hyperlinks to collaborators

User story

As a developer/designer,
I want the option to view the a collaborator's CRC Model
In order to examine the relationship between collaborators and the objects that depends on them.

Acceptance criteria

1. Collaborators themselves are hyperlinked to their Class/Object definition source code's branch from which the report was generated.
2. Each collaborator has hyperlinked to the line numbers in which the dependent Class/Object declares them.
3. The declaration links are in the format of [line-number:column-number], e.g., [20:18].

Add BDD test results to CircleCI

User story

~~As a contributor and stakeholder, I want to view spec results from CircleCI.~~

~~See CircleCI docs for Mocha for Node.js.~~

As a stakeholder,
I want to remove redundant CI services
For faster builds and assessment.

Acceptance criteria

Remove these CI services:

1. CircleCI. Use Travis-CI instead.
2. Coverity (appears to be a paid service, now)
3. Snyk (this is covered by Bithound)

Scope creep! 😱

4. Fix Bithound lint issues.
5. Achieve 100% code coverage

feat(reports): hyperlink object names to source code

User story

As a developer/designer,
I must be able to quickly evaluate the source code of the Class/Object modeled
in order to analyze it quickly.

Acceptance criterion

The link goes to the Class/Object file of the repository branch from which the report was generated.

Add logging

Issue type

Enhancement/feature request

Expected Behavior

Create standard logs that can be appended to

Console
File
HTTP requests

Current Behavior

N/A.

Possible Solution: `winston`

winston appears to be the most popular logging solution for Nodejs. See NPMCompare's comparison of bunyan vs. log4js vs. winston.

Context

Your Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your project:

Add automated build and quality tools to product

User story

As a developer, tester, and build engineer, I need to automate common tasks in order to deliver features and fixes faster with better quality.

Acceptance criteria

- Automate BDD spec (unit test) execution
- ~~Add watcher to execute specs on file save~~
  Not doing for now. I'll likely add gulp to make life easier soon. In the meantime, CLI history suffices.
- ~~Append CHANGELOG whenever there is a semver change~~
  npm run changelog is working fine, for now. After I add gulp, I'll install plugins to handle bumps, changelogs, *.json version updates, and releases.
- Generate documentation
- ~~Add code coverage and spec results coveralls.io~~ Codacy has this feature, already.
- Add CI tasks for multiple Node.js versions on travis-ci
- Add third-party quality analysis Codacy
- Display coverage, CI, and quality rates as badges in README

An in-range update of sinon is breaking the build 🚨

Version 2.3.5 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details

Release Notes

Fix: Check configurable on a prop before creating

Check configurable on a prop before creating (fixes #1456) (#1462)

Commits

The new version differs by 8 commits.

33f32ac Update docs/changelog.md and set new release id in docs/_config.yml
d00ab2b Add release documentation for v2.3.5
1c690aa 2.3.5
cc0a3fb Update Changelog.txt and AUTHORS for new release
ef2ecec Check configurable on a prop before creating (fixes #1456) (#1462)
e7dbfd7 Merge pull request #1460 from gj/patch-1
512018f Fix minor typos
d60d4a2 Fix apostrophe typos (#1454)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of coveralls is breaking the build 🚨

Version 2.13.0 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.12.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Code 1 failing file. Details
❌ bitHound - Dependencies 5 failing dependencies. Details

Commits

The new version differs by 4 commits .

2821200 version bump
ef7e811 Parse commit from packed refs if not available in refs dir. (#163)
e476964 Merge pull request #162 from evanjbowling/patch-1
63a7f92 Update README.md

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of babel-register is breaking the build 🚨

Version 6.24.1 of babel-register just got published.

Branch	Build failing 🚨
Dependency	babel-register
Current Version	6.24.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-register is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
✅ bitHound - Code No failing files. Details
❌ bitHound - Dependencies 3 failing dependencies. Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

chore(packages): fix security vulnerabilities

User story

As a developer and consumer,
I need eslint-plugin-crc to be secure
In order to confidently use it.

Acceptance criteria

All required third-party CI-services pass.

build(dependencies): update outdated packages

Epic

As an plugin producer and consumer,
I must update this module's dependencies
In order to avoid security vulnerabilities.

An in-range update of coveralls is breaking the build 🚨

Version 2.13.1 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.13.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/201421),- ✅ **codeclimate/coverage** 100% [Details](https://codeclimate.com/github/gregswindle/eslint-plugin-crc),- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/gregswindle/eslint-plugin-crc/builds/226574786),- ✅ **coverage/coveralls** First build on greenkeeper/coveralls-2.13.1 at 100.0% [Details](https://coveralls.io/builds/11278135),- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/a8f62ae9e53e21d18ed9111548ff67c95b1526be/dependencies/npm?status=passing),- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/a8f62ae9e53e21d18ed9111548ff67c95b1526be/files#filter-failing-file)

Commits

The new version differs by 1 commits0.

b9032a1 better Jenkins detection

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of minami is breaking the build 🚨

Version 1.2.2 of minami just got published.

Branch	Build failing 🚨
Dependency	minami
Current Version	1.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As minami is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Dependencies 3 failing dependencies. Details
✅ bitHound - Code No failing files. Details

Commits

The new version differs by 2 commits .

27b5856 1.2.2
89a6299 fix(publish): tutorial has no kind, fix #30

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

feat(printing): paginate printed reports with one CRC model per page

User story

As an software product delivery stakeholder,
I want to print CRC reports with one CRC model per page
In order to facilitate collocated design discussions.

Acceptance criteria

1. Printed copies of CRC Model reports have one and only one CRC model per page.
2. If GitHub-flavored markdown does not support features like CSS's page-break-after, CRC Model reports should support an option that does, e.g., PDF.

⚡ Rule developers must use the `eslint:rule` subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

Create a stubbed rule,

The rule's stubbed BDD specs,

As well as the rule's documentation.

See eslint-plugin development environment for details.

An in-range update of nsp is breaking the build 🚨

Version 2.7.0 of nsp just got published.

Branch	Build failing 🚨
Dependency	nsp
Current Version	2.6.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nsp is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details

Commits

The new version differs by 13 commits.

e88fb8a 2.7.0
f207e03 fix package.json so things actually work
11d5635 Merge pull request #178 from nodesecurity/quiet-flag
cf32c95 remove unused code
5ee23ec Merge pull request #164 from dblandin/devon/update-dockerfile
c41e59d Pick Lint
a9491bd Add quiet to --output usage
215432f add quiet output
c20afb3 drone config
d9ba63b Update Dockerfile
73c321d Merge pull request #158 from koresar/patch-1
904dc3e Make sure the table width is a minimum width
da2b275 Fix nsp CLI crash in the no window (CI) envs

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 2.3.2 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ bitHound - Code 2 failing files. Details
❌ bitHound - Dependencies 1 failing dependency. Details
✅ codeclimate/coverage 100% Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/sinon-2.3.2 at 100.0% Details

Release Notes

Minor fixes

Fix failing sandbox.resetBehavior() (#1428)
Fix restoring getters/setters/values for previously unexisting props (#1419)
Called in order takes callCount into account. Closes #1398.

Commits

The new version differs by 17 commits.

2463d10 Update docs/changelog.md and set new release id in docs/_config.yml
2e6bb45 Add release documentation for v2.3.2
87abc01 2.3.2
96e8abe Update Changelog.txt and AUTHORS for new release
2f941e2 Merge pull request #1406 from lucasfcosta/called-in-order-considers-callcount
3af985a Merge pull request #1427 from fearphage/remove-try-from-tests
c81d76b Merge pull request #1428 from fatso83/failing-sandbox-reset
0bf0a79 Fix failing sandbox.resetBehavior()
be4e53b Add failing tests for sandbox.reset()
fe049aa Add code snippet for createStubInstance (#1423)
9e23c4a added rule to prevent try-catch usage in tests
528a7dc switched from try-catch to assert.exception()
d8dac84 Add downloads per month banner to README.md
e933add Add site/_docs/ to .eslintignore
ebe37da Add documentation for "has" matcher on embedded objects (#1422)

There are 17 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of codacy-coverage is breaking the build 🚨

Version 2.0.2 of codacy-coverage just got published.

Branch	Build failing 🚨
Dependency	codacy-coverage
Current Version	2.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codacy-coverage is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Dependencies Details
❌ bitHound - Code Details
❌ dependency-ci Failed dependency checks Details

Commits

The new version differs by 6 commits .

0ee0002 Release version 2.0.2
749f3f4 Merge pull request #41 from codacy/detect-files-language
c31dadf Detect files language and send separate reports per language
8b149e6 Merge pull request #40 from lapa182/patch-1
efd669a Fix markdown typo issue
6f71931 Add language docs

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of chai is breaking the build 🚨

Version 4.1.0 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ dependency-ci Dependencies checked Details

Release Notes

4.1.0 / 2017-07-11

This release includes one new feature and a few bug fixes.

New Features

Add ES6 collection support to include() (#970, #994; @shvaikalesh)

Bug Fixes

Allow dates for isBelow and isAbove assertions (#980, #990; @v1adko)
fix: check target's type in .property assertion (#992; @meeber)

Chores

Add a missing var keyword found by lgtm.com (#988; @samlanning)
refactor: expectTypes to access ssfi flag (#993; @meeber)
Create CODEOWNERS (#1004; @keithamus)

Commits

The new version differs by 16 commits.

df9073c Merge pull request #998 from v1adko/make-release
cad9933 Merge pull request #1004 from chaijs/code-owners
cf70b11 Create CODEOWNERS
3397dda Merge pull request #1005 from meeber/skip-failing-tests
11a6f85 test: skip failing .include tests in IE11
45cb327 [email protected]
2eddd79 Add ES6 collection support to include() (#994)
3c932e2 feat: allow dates for isBelow and isAbove assertions (#990)
3bcb21c Merge pull request #979 from chaijs/greenkeeper/browserify-14.4.0
5daceab Merge pull request #988 from samlanning/missing-var
9116bc8 Merge pull request #993 from meeber/refactor-expect-types
351e968 Merge pull request #992 from meeber/property-target-type
e7b2384 refactor: expectTypes to access ssfi flag
e6ddf64 fix: check target's type in .property assertion
7e466af Add a missing var keyword found by lgtm.com

There are 16 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 2.3.3 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Code 2 failing files. Details
❌ bitHound - Dependencies 2 failing dependencies. Details

Release Notes

Make stubbing of static function properties possible

Fix #1450, make stubbing of static function properties possible

Commits

The new version differs by 24 commits.

bade318 Update docs/changelog.md and set new release id in docs/_config.yml
65d4e88 Add release documentation for v2.3.3
2204e72 2.3.3
64034ee Update Changelog.txt and AUTHORS for new release
1ece07c Merge pull request #1450 from raulmatei/fix-1445-sandbox-stubbing-static-function-property-throws-error
452981c Fix 1445: make stubbing of static function properties possible
25f3eeb Update sandbox configuration docs. (#1443)
c76fa2e Merge pull request #1444 from piperchester/patch-1
6539d94 Update README.md
c6d01d8 Add missing function name (#1440)
5f989a8 Remove confusing .withArgs from spy documentation (#1438)
9ca272e Remove superfluous calls in example (#1437)
9e3eac3 Merge pull request #1436 from sinonjs/feature-detect-name-property
65d3d7b Feature detect function name property in issue 950
e0c75bd Add test for #950, show that it has been fixed (#1435)

There are 24 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Display "class name" prototypes (if applicable)

User story

As a developer/designer, I must see whether a Class/Object is a prototype of another Class/Object in order to further evaluate inheritance dependencies.

Acceptance criteria

Note: by "Class", we mean the "subject" of a CRC mode.

A Class's prototype is displayed, if it has one.
The prototype is hyperlinked to its associated source code in the branch from which the report was generated.

build(dependencies): update all packages

User story

As a plugin consumer or contributor,
I need development and production dependencies to be up-to-date
In order to mitigate security risks.

Acceptance criteria

1. All production dependencies are up-to-date.
2. All development dependencies are up-to-date.
3. The plugin's QA checks pass.

An in-range update of espree is breaking the build 🚨

Version 3.4.3 of espree just got published.

Branch	Build failing 🚨
Dependency	espree
Current Version	3.4.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ bitHound - Code null Details,- ❌ bitHound - Dependencies null Details,- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ❌ dependency-ci Failed dependency checks Details

Release Notes

v3.4.3

343590a Fix: add AwaitExpression to espree.Syntax (fixes #331) (#332) (Teddy Katz)

Commits

The new version differs by 3 commits0.

ea08611 3.4.3
4ecb96a Build: changelog update for 3.4.3
343590a Fix: add AwaitExpression to espree.Syntax (fixes #331) (#332)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.2.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **bitHound - Code** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fnyc-10.3.0),- ❌ **bitHound - Dependencies** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fnyc-10.3.0),- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/gregswindle/eslint-plugin-crc/builds/227080704?utm_source=github_status&utm_medium=notification),- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/202425)

Commits

The new version differs by 4 commits ahead by 4, behind by 2.

55e826d chore(release): 10.3.0
89dc7a6 chore: explicit update of istanbul dependnecies (#562)
1887d1c feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18 fix: source-maps were not being cached in the parent process when --all was being used (#556)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

feat(responsibilities): extract object responsibilities from JSDoc comments

User story

As an engineer, analyst, or designer,
I need to understand an object's stated purpose
In order to determine whether its design could be improved.

Acceptance criteria

1. doctrine parses JSDoc comments to createResponsibility objects.
2. Responsibility objects are associated with source objects.
3. Responsibilities are output as enumerated lists in a CRC Model's "Responsibilities" section.
4. Class descriptions display under a CRC Model's Name whenever JSDoc annotations exist for them.

refactor(eslint:rules): collect CrcModels during standard rule evaluation

User story

As an eslint-plugin-* developer and consumer,
I want to use ESLint's standard rules and processors
In order to create CRC models consistently.

Acceptance criteria

1. A custom formatter/crc/ generates CrcModel reports.
2. lib/crc/ generates a JSON data structure for class-responsibilities-collaborators.

Test ticket from Code Climate

An in-range update of uglify-js is breaking the build 🚨

Version 3.0.14 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.0.13
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As uglify-js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ bitHound - Dependencies 1 failing dependency. Details
❌ bitHound - Code 2 failing files. Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details

Release Notes

v3.0.14

Commits

The new version differs by 3 commits.

3e62faa v3.0.14
e9645e0 introduce unsafe_Func (#2033)
55b5f2a widen CLI parse error code fragment displayed (#2032)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

chore(semantic-intent): discuss applicability of Conceptual Graphs to infer software's semantic intent with John Sowa

Issue type

Feedback, suggestions, or questions

Expected Behavior

Provide AI-generated responsibilities based on AST structure, identifier names, code comments, and JSDoc annotations.

Current Behavior

This project is still in its research phase.

Possible Solution

I'm particularly interested in whether John Sowa's Conceptual Graphs would be useful for discovering and expressing the semantic intent of source code. Dr. Sowa's email address appears to be [email protected].

Your Environment

Version used

N/A. The immediate groundwork is based on Nodejs v7.7.3, but I'll evaluate other languages:

Scala
Python

Operating System and version (desktop)

💻 Mac environment info
Run the following commands from a Terminal, then copy and paste them here:

sw_vers && uname

system_profiler (optional: this takes several minutes to complete)

ProductName:	Mac OS X
ProductVersion:	10.12.4
BuildVersion:	16E195
Darwin

Link to your project

eslint-plugin-crc

An in-range update of nyc is breaking the build 🚨

Version 11.0.3 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 4 commits.

e9fad9f docs: add note about tap-nyc to README (#614)
f86b0b1 chore(release): 11.0.3
923b062 fix: upgrade to spawn-wrap version that works with babel-register (#617)
b1eb4d6 fix: update help link to list of reporters (#601)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

build(monitoring): setup Airbrake for eslint-plugin-crc

Install Airbrake in 2 easy steps:

Step 1: Add the library
Include via CDN:

<script src="https://cdnjs.cloudflare.com/ajax/libs/airbrake-js/1.0.4/client.min.js"></script>

We also support installation via npm and Bower.

Step 2: Copy this config snippet to your app.js file

(You can find your project ID and API KEY with your project's settings):

var airbrake = new airbrakeJs.Client({
  projectId: <Your project ID>,
  projectKey: '<Your project API Key>'
});
airbrake.addFilter(function (notice) {
  notice.context.environment = 'production';
  return notice;
});

To test that Airbrake has been installed correctly in your JavaScript project, just open up the JavaScript console in your internet browser and paste in:

airbrake.notify('hey there!')

Visit official GitHub repo for more info on alternative configurations and advanced options.

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/gregswindle/eslint-plugin-crc/builds/225146654),- ❌ **bitHound - Dependencies** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fmocha-3.3.0),- ❌ **bitHound - Code** null [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-crc/greenkeeper%2Fmocha-3.3.0),- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/198509)

Release Notes

coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

We've got coverage now!
Testing is looking less flaky \o/.
No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
#2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

#2672: Add coverage for node tests (@c089, @Munter)
#2680: Increase tests coverage for base reporter (@epallerols)
#2690: Increase tests coverage for doc reporter (@craigtaub)
#2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)
#2691: Increase tests coverage for spec + dot reporters (@craigtaub)
#2698: Increase tests coverage for xunit reporter (@craigtaub)
#2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)
#2703: Cover .some() function in utils.js with tests (@seppevs)
#2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)

🔩 Other

Remove bin/.eslintrc; ensure execs are linted (@boneskull)
#2542: Expand CONTRIBUTING.md (@boneskull)
#2660: Double timeouts on integration tests (@Munter)
#2653: Update copyright year ([@Scottkao85], @Munter)
#2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)
#2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)
#2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)
Add Mocha propaganda to README.md (@boneskull)
#2470: Avoid test flake in "delay" test (@boneskull)
#2675: Limit browser concurrency on sauce (@boneskull)
#2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)
Fix "projects" link in README.md (@boneskull)
#2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)
#2648: Use semistandard directly (@kt3k)
#2727: Make the build reproducible (@lamby)

Commits

The new version differs by 89 commits0.

fb1687e :ship: Release v3.3.0
1943e02 Add Changelog for v3.3.0
861e968 Refactor literal play-icon hex code to a var
1d3c5bc Fix typo in karma.conf.js
9bd9389 Fix spec paths in test HTML files
0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
73929ad Comment special treatment of '+' in URL query parsing
e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
038c636 Support --inspect-brk on command-line
b4ebabd Merge pull request #2727 from lamby/reproducible-build
882347b Please make the build reproducible.
a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
ed61cd0 cover .some() function in utils.js with tests
f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
6065242 use stubbed symbol

There are 89 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of espree is breaking the build 🚨

Version 3.4.1 of espree just got published.

Branch	Build failing 🚨
Dependency	espree
Current Version	3.4.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As espree is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
✅ bitHound - Code No failing files. Details
❌ bitHound - Dependencies 5 failing dependencies. Details

Release Notes

v3.4.1

a3ae0bd Upgrade: acorn to 5.0.1 (#327) (Teddy Katz)
15ef24f Docs: Add badges (#326) (Jan Pilzer)
652990a Fix: raise error for trailing commas after rest properties (fixes #310) (#323) (Teddy Katz)
9d86ba5 Upgrade: acorn to ^4.0.11 (#317) (Toru Nagashima)
a3442b5 Chore: fix tests for Node 6+ (#315) (Teddy Katz)

Commits

The new version differs by 7 commits .

d5d1808 3.4.1
aea631f Build: changelog update for 3.4.1
a3ae0bd Upgrade: acorn to 5.0.1 (#327)
15ef24f Docs: Add badges (#326)
652990a Fix: raise error for trailing commas after rest properties (fixes #310) (#323)
9d86ba5 Upgrade: acorn to ^4.0.11 (#317)
a3442b5 Chore: fix tests for Node 6+ (#315)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Generate report files from the CLI

User story

As as developer/designer, I want to generate CRC models from a command line interface in order to automate design documents.

Acceptance criteria

1. Generate CRC models for a single file.
2. Generate CRC models for a directory, recursively, with glob patterns.
3. The CRC models will be on a single "page," e.g., crc-models.md.
4. The report displays:
- a. The date and time that the report was generated.
- b. The repository branch revision from which the report was generated.

~~5. The CRC Models can be restricted by Expression or Declaration type.~~

An in-range update of jsdoc is breaking the build 🚨

Version 3.5.0 of jsdoc just got published.

Branch	Build failing 🚨
Dependency	jsdoc
Current Version	3.4.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As jsdoc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details

Release Notes

JSDoc 3.5.0

This version of JSDoc includes the following major changes:

JSDoc now uses the Babylon JavaScript parser, which means that
JSDoc can parse any JavaScript or JSX file that is supported by the Babel
compiler.
You can now use a JavaScript file to configure JSDoc. See the
documentation for details and examples.
Fixed multiple issues with documenting ES2015 classes and modules.
JSDoc now requires Node.js 4.2.0 or later.

For a complete list of changes, see the changelog on GitHub.

Commits

The new version differs by 112 commits ahead by 112, behind by 45.

cdd00c0 3.5.0
50d6119 update 3.5.0 changelog
e94a598 3.5.0 changelog
5d0b690 reformat changelog
c50a4c0 add yields tag (#1388)
f31a011 resolve the path to the JS config file before requiring it (#1386)
d95cbdd support namespaces that are also functions (#955)
9f8853a add hideconstructor tag (#952)
ca1c4f2 add package tag (#962)
6275e69 autodetect default and repeatable parameters when a function is assigned to a variable (#1054)
0e4f1a9 correctly document constructors and instance properties of ES2015 classes (#1182)
67db938 add sourceType config option
f101798 fix crash when the author tag is empty (#1289)
43a117d add recurseDepth config option (#1340)
8f5c60b support bigint

There are 112 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

doc(community-standards): update community documents

User story

As an a consumer or contributer,
I need clear and succinct instructions
In order to use or collaborate on eslint-plugin-crc.

Acceptance criteria

commonality/generator-community has updated:

⚡ Rule developers must use the `eslint:rule` subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

Create a stubbed rule,

The rule's stubbed BDD specs,

As well as the rule's documentation.

See eslint-plugin development environment for details.

An in-range update of uglify-js is breaking the build 🚨

Version 2.8.22 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	2.8.21
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Dependencies 3 failing dependencies. Details
✅ bitHound - Code No failing files. Details

Release Notes

v2.8.22

Commits

The new version differs by 21 commits .

04b8964 v2.8.22
d6fbc36 fix LHS cases for NaN & friends (#1804)
9a97884 enhance test/ufuzz.js (#1803)
0479ff0 fix a couple of bugs in global_defs (#1802)
cf72fe5 fix delete corner cases (#1799)
a1532eb extend ufuzz generator (#1783)
c2a1bce fix pure_getters for chained property access (#1798)
e3c9c22 fix corner cases with delete (#1796)
0f4cd73 introduce "strict" to pure_getters (#1795)
281e882 fix reduce_vars on catch variable (#1794)
cc6aa3e fix incorrect context in variable substitution (#1791)
e869779 enable inline_script by default (#1793)
06cdb74 improve pure_getters (#1786)
ff289b9 implement delayed resolution for reduce_vars (#1788)
9b6bc67 optimise do{...}while(false) (#1785)

There are 21 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of uglify-js is breaking the build 🚨

Version 3.0.16 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.0.15
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 19 failing files. Details

Release Notes

v3.0.16

Commits

The new version differs by 23 commits.

4231f73 v3.0.16
da2de35 add comment about quote_style and gzip (#2092)
41beae4 cache web assets between CI runs (#2089)
82db918 fix CLI parsing of --source-map content (#2088)
3dc9e14 add Node.js 8 to Travis CI (#2086)
fed0096 allow expect_stdout to specify Error (#2087)
2bdc880 fix variable accounting in inline (#2085)
5ef7cb3 suppress false positives for-in loops (#2080)
4ad7b1d fix portability of sandbox.run_code() on Node.js 0.1x (#2078)
9186859 fix non-string parameters (#2076)
47c0713 report test/ufuzz.js failures in process.stderr (#2074)
293c566 marshal mangle[.properties].reserved from non-Array values (#2072)
9c30640 fix iteration over object with inherited properties (#2068)
9db0695 fix cascade on multi-branch evaluations (#2067)
f2af093 fix CLI output corruption (#2061)

There are 23 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

ci(release): publish to NPM

Expected Behavior

I should be able to install the plugin from NPM.

Current Behavior

It is not available in NPM.

$ npm install eslint-plugin-crc
npm ERR! Darwin 16.7.0
npm ERR! argv "/Users/jeffrose/.nvm/versions/node/v6.10.2/bin/node" "/Users/jeffrose/.nvm/versions/node/v6.10.2/bin/npm" "install" "eslint-plugin-crc"
npm ERR! node v6.10.2
npm ERR! npm  v4.3.0
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/eslint-plugin-crc
npm ERR! 404 
npm ERR! 404  'eslint-plugin-crc' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

An in-range update of sinon is breaking the build 🚨

Version 2.3.4 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
✅ dependency-ci Dependencies checked Details
❌ bitHound - Dependencies 2 failing dependencies. Details
❌ bitHound - Code 2 failing files. Details

Release Notes

Make sandbox.resetHistory also reset spies

Fix #1372: make sandbox.resetHistory also reset spies (#1424)

Commits

The new version differs by 5 commits.

72ae300 Update docs/changelog.md and set new release id in docs/_config.yml
769d770 Add release documentation for v2.3.4
c8d2ec0 2.3.4
d27976a Update Changelog.txt and AUTHORS for new release
330101a Fix #1372: make sandbox.resetHistory also reset spies (#1424)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

feat(complexity): summarize cyclomatic complexity metrics for each CrcModel.class

User story

As an API producer and consumer,
I want to quickly assess every object's cyclomatic complexity
In order to identify objects that might require refactoring.

Acceptance criteria

1. CrcModel.prototype has a meta object.
2. CrcModel.prototype.meta has a property called complexity.
3. meta.complexity provides complexity metrics for every "class".

chore(package): update eslint to latest

User story

As a plugin consumer,
I need dependencies to be up-to-date
In order to avoid security vulnerabilities.

Acceptance criteria

Update eslint to ^4.0.0

feat(nlp): parse source code for semantic intent

User story

As an API producer and consumer,
I want to understand the design of undocumented legacy code with natural language
In order to understand it and refactor as needed.

Acceptance criteria

1. {criterion-one}
2. {criterion-two}
3. {criterion-three}
4. {criterion-four}

⚡ Rule developers must use the `eslint:rule` subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

Create a stubbed rule,

The rule's stubbed BDD specs,

As well as the rule's documentation.

See eslint-plugin development environment for details.

An in-range update of dirty-chai is breaking the build 🚨

Version 2.0.1 of dirty-chai just got published.

Branch	Build failing 🚨
Dependency	dirty-chai
Current Version	2.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As dirty-chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ dependency-ci Dependencies checked Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details

Commits

The new version differs by 6 commits.

53a0def 2.0.1
4f524c3 Merge pull request #28 from perrin4869/master
909802d Fix compatibility with chai-as-promised with chai@4
f82d79e Merge pull request #24 from prodatakey/multichai-testing
182f3f7 Fix travis conf
8b330f1 Test multiple chai versions

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

gregswindle / eslint-plugin-crc Goto Github PK

eslint-plugin-crc's People

Contributors

Stargazers

Watchers

Forkers

eslint-plugin-crc's Issues

Epic summary

Acceptance criteria

⚡ Rule developers must use the eslint:rule subgenerator!

User story

Acceptance criteria

⚡ Rule developers must use the eslint:rule subgenerator!

Version 3.4.2 of espree just got published.

Version 10.2.0 of nyc just got published.

Issue type

User story

Acceptance criterion

Possible Solutions

Context

Version 2.2.0 of codecov just got published.

Tasks

Version 3.19.0 of eslint just got published.

User story

Acceptance criteria

User story

Acceptance criteria

Scope creep! 😱

User story

Acceptance criterion

Issue type

Expected Behavior

Current Behavior

Possible Solution: winston

Context

Your Environment

User story

Acceptance criteria

Version 2.3.5 of sinon just got published.

Version 2.13.0 of coveralls just got published.

Version 6.24.1 of babel-register just got published.

User story

Acceptance criteria

Epic

Version 2.13.1 of coveralls just got published.

Version 1.2.2 of minami just got published.

User story

Acceptance criteria

⚡ Rule developers must use the eslint:rule subgenerator!

Version 2.7.0 of nsp just got published.

Version 2.3.2 of sinon just got published.

Version 2.0.2 of codacy-coverage just got published.

Version 4.1.0 of chai just got published.

New Features

Bug Fixes

Chores

Version 2.3.3 of sinon just got published.

User story

Acceptance criteria

User story

Acceptance criteria

Version 3.4.3 of espree just got published.

Version 10.3.0 of nyc just got published.

User story

Acceptance criteria

User story

Acceptance criteria

Version 3.0.14 of uglify-js just got published.

Issue type

Expected Behavior

Current Behavior

Possible Solution

Your Environment

Version used

Operating System and version (desktop)

Link to your project

Version 11.0.3 of nyc just got published.

Install Airbrake in 2 easy steps:

Version 3.3.0 of mocha just got published.

🎉 Enhancements

⚡ Rule developers must use the `eslint:rule` subgenerator!

⚡ Rule developers must use the `eslint:rule` subgenerator!

Possible Solution: `winston`

⚡ Rule developers must use the `eslint:rule` subgenerator!

⚡ Rule developers must use the `eslint:rule` subgenerator!