Skip to content

Commit

Permalink
Add 2019-06-06 meeting notes (closes #134)
Browse files Browse the repository at this point in the history
  • Loading branch information
btmills committed Jun 6, 2019
1 parent 483b6ce commit 03b7134
Showing 1 changed file with 38 additions and 0 deletions.
38 changes: 38 additions & 0 deletions notes/2019/2019-06-06.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# 2019-June-06 ESLint TSC Meeting Notes

## Transcript

https://gitter.im/eslint/tsc-meetings/archives/2019/06/06

## Attending

* Brandon Mills (@btmills) - TSC
* Toru Nagashima (@mysticatea) - TSC
* Kai Cataldo (@kaicataldo) - TSC
* Teddy Katz (@not-an-aardvark) - TSC
* Ilya Volodin (@ilyavolodin) - TSC

Additionally, the following individuals are not in attendance but support consensus:

* Nicholas C. Zakas (@nzakas) - TSC
* Gyandeep Singh (@gyandeeps) - TSC

## Topics

### [New: Recoverable Error Handling](https://github.com/eslint/tsc-meetings/issues/134#issuecomment-499588193)

**TSC Summary:** [README.md](https://github.com/eslint/rfcs/blob/handling-recoverable-errors/designs/2019-recoverable-error-handling/README.md)

* @platinumazure suggested using a loose parsing mode in a [pull request review](https://github.com/eslint/eslint/pull/11509#pullrequestreview-220174854).
* @mysticatea has implemented recoverable errors in `vue-eslint-parser`, and TypeScript has recoverable errors as well.
* We should try to avoid cases where additional errors and potential false positives due to invalid AST could confuse users or introduce additional complexity.
* @btmills suggests showing as many parser errors as we can but only running lint rules once the parser passes successfully.
* @platinumazure suggests adding an option to `parserOptions` that would error immediately like the current behavior, show all parser errors, or show all recoverable errors and run lint rules.
* :+1: to showing all recoverable errors at once from @btmills, @kaicataldo, @ilyavolodin, @mysticatea, @platinumazure. Details to be decided in the RFC.
* Though this could technically show more errors at one time, it will not show any errors where there weren't any already, so this does not have to be a breaking change. @btmills, @kaicataldo, and @platinumazure agree. Nobody against.

**Resolution**: @mysticatea will update the RFC to show all recoverable errors at once by default.

### [Scheduled release for June 7th, 2019](https://github.com/eslint/eslint/issues/11768)

**Resolution**: @platinumazure and @ilyavolodin will do the release.

0 comments on commit 03b7134

Please sign in to comment.