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

(feat): support JS & JSX files in tsdx lint #487

Merged
merged 1 commit into from
Feb 4, 2020

Conversation

agilgur5
Copy link
Collaborator

@agilgur5 agilgur5 commented Feb 3, 2020

  • JS & JSX are already supported in tsdx build, so this is just adding
    some better parity in tsdx test

    • more JS & JSX support also means better support for gradual TS
      migrations
  • prior to this, JS & JSX files wouldn't be linted unless explicitly
    included with a glob or something

    • extensions is also only configurable via CLIEngine, .eslintrc
      doesn't currently support it
  • fix errors & warnings in JS test files as TSDX dogfoods its own lint
    functionality

I'm currently adding TSDX in https://github.com/agilgur5/react-signature-canvas while migrating it to TS and this came up as frustration. Related to #486

EDIT: For posterity, here's my PR agilgur5/react-signature-canvas#42, and specifically agilgur5/react-signature-canvas@2980b8a is where this popped up -- note the custom package.json lint script.

- JS & JSX are already supported in tsdx build, so this is just adding
  some better parity in tsdx test
  - more JS & JSX support also means better support for gradual TS
    migrations

- prior to this, JS & JSX files wouldn't be linted unless explicitly
  included with a glob or something
  - extensions is also only configurable via CLIEngine, .eslintrc
    doesn't currently support it

- fix errors & warnings in JS test files as TSDX dogfoods its own lint
  functionality
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants