Closed bryannho closed 1 year ago
eslint was already included in the package.json
so I simply created a config file with npm init @eslint/config
. If we want to use a newer version of eslint I can update it in the package.json
can you check the CI? Looks like since we added this, now the linter is running automatically.
can you check the CI? Looks like since we added this, now the linter is running automatically.
It looks like it's running pkgmt lint
as defined in ci.yaml
but not eslint as I didn't modify ci.yaml
to include that. Was this the intended behavior?
the CI test failed on my first commit because of the edit I made to tsconfig.json
but now it seems to be failing because of an issue with widgets.ipynb
. is this related to the issue with @jupyter-widgets/base
?
@edublancas could you please review? just pinging in case you weren't notified
Describe your changes
Issue number
Closes #76
Checklist before requesting a review
pkgmt format