-
Notifications
You must be signed in to change notification settings - Fork 242
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: jest-community/eslint-plugin-jest
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v24.5.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: jest-community/eslint-plugin-jest
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v24.6.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 9 files changed
- 2 contributors
Commits on Oct 9, 2021
-
Configuration menu - View commit details
-
Copy full SHA for a4f66f6 - Browse repository at this point
Copy the full SHA a4f66f6View commit details -
feat(valid-expect-in-promise): re-implement rule (#916)
* feat(valid-expect-in-promise): re-write implementation * fix(valid-expect-in-promise): check number of arguments being passed * fix(valid-expect-in-promise): bailout if `done` callback is present * fix(valid-expect-in-promise): allow awaited promises * fix(valid-expect-in-promise): handle multi-chained promises properly Method call chains are represented in AST in a nested fashion, meaning it's not enough to just separately track if we're both in a promise chain call and then if we've found an `expect` call, because when we exit another CallExpression in the same chain it'll look like that has an `expect` call. Instead, we need to track our depth as we enter CallExpression nodes so that when we exit those nodes we can check if we encountered an `expect` call at that same depth. * fix(valid-expect-in-promise): handle promises assigned to variables * refactor(valid-expect-in-promise): adjust conditions to dedent code * fix(valid-expect-in-promise): allow variables assigned awaited promises * feat(valid-expect-in-promise): track promise vars across reassignments * feat(valid-expect-in-promise): support blocks and multi-variable assigns * feat(valid-expect-in-promise): support re-assignment promise chaining * refactor(valid-expect-in-promise): remove unneeded condition * refactor(valid-expect-in-promise): inline reporting function We only call it in one place, and so it lets us also remove some minor types that can be otherwise inferred * fix(valid-expect-in-promise): rewrite rule message to be clearer * fix(valid-expect-in-promise): rewrite rule description to be clearer * fix(valid-expect-in-promise): ignore unreachable code after return * fix(valid-expect-in-promise): support `Promise.all` * fix(valid-expect-in-promise): support `resolve` & `reject` methods * refactor(valid-expect-in-promise): remove unneeded optional chain * refactor(valid-expect-in-promise): adjust conditions slightly * chore(valid-expect-in-promise): add a bunch of comments * feat(valid-expect-in-promise): support `Promise.allSettled` * docs(valid-expect-in-promise): add more examples and reword
Configuration menu - View commit details
-
Copy full SHA for 7a49c58 - Browse repository at this point
Copy the full SHA 7a49c58View commit details -
chore(release): 24.6.0 [skip ci]
# [24.6.0](v24.5.2...v24.6.0) (2021-10-09) ### Features * **valid-expect-in-promise:** re-implement rule ([#916](#916)) ([7a49c58](7a49c58))
Configuration menu - View commit details
-
Copy full SHA for cc12c7c - Browse repository at this point
Copy the full SHA cc12c7cView commit details
There are no files selected for viewing