Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: backport non-breaking changes from next #607

Merged
merged 6 commits into from Jun 21, 2020

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Jun 21, 2020

Does what it says in the title. Reduces the diff between master & next - the main ones I wanted were the eslint rules, tsconfig target change, and code restructures, but figured I'd bring a few things along just to reduce the diff further.

This is required for using private identifiers, which are used by
`@typescript-eslint` v3.

We don't use `tsc` to actually build any code, so this change only
affects the typechecking side of the compiler.
`@typescript-eslint` v3 changed the structure of their types, meaning
that we need to type the options for `valid-title`.

This in turn means we have to provide a direct default value for the
`disallowedWords` option, in turn meaning we have to adjust our test to
ensure proper coverage instead of relying on the `default` property.
`@typescript-eslint` v3 changed the structure of their types, meaning
that the `suggest` property in `TSESLint.ReportDescriptor` is now marked
 as being `readonly`, so we can't assign to it.

The easiest way around this is to just refactor our code to be slightly
different, given it doesn't impact behaviour, performance, or clarity.
@G-Rath G-Rath merged commit c179c7c into master Jun 21, 2020
@G-Rath G-Rath deleted the backport-some-safe-changes-from-next branch June 21, 2020 04:19
@github-actions
Copy link

🎉 This PR is included in version 23.15.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant