Skip to content
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.

Fix/upgrade linting #298

Merged
merged 6 commits into from
Dec 17, 2019
Merged

Fix/upgrade linting #298

merged 6 commits into from
Dec 17, 2019

Conversation

bryanstearns
Copy link
Member

When starting to work on finishing #275, I noticed that yarn lint for the Bowser project itself (that is, not the generated app) was really linting the compiled javascript instead of the original typescript.

Fixing that got me a complaint that the typescript-eslint parser & plugin weren't compatible with my version of Typescript (which always seems to be "latest" because we don't commit our yarn.lock, and because of yarn hoisting... I think).

So I upgraded them, and fixed a few new complaints they produced. I also upgraded them in the generated apps, and fixed new (but different!) complaints there.

Running the tests (in the outer project) will now also lint (with --fix), just to help keep things linty-fresh. (CI will also lint, but without --fix.)

…tests too

Also:
- for now, don't --fix when linting; will add it back for devs (but not CI) later
- clean up tsconfig.json's include/exclude lists
…ix new complaints

- don't ban @ts-ignore
- use comments on two intentially-empty functions
- add index.js to tsconfig.json
@jamonholmgren jamonholmgren merged commit a8e40d8 into master Dec 17, 2019
@jamonholmgren jamonholmgren deleted the fix-lint branch December 17, 2019 20:23
infinitered-circleci pushed a commit that referenced this pull request Dec 17, 2019
## [4.11.4](v4.11.3...v4.11.4) (2019-12-17)

### Bug Fixes

* **linting:** Fixes linting of newly generated apps ([#298](#298) by [@bryanstearns](https://github.com/bryanstearns)) ([a8e40d8](a8e40d8))
@infinitered-circleci
Copy link

🎉 This PR is included in version 4.11.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants