Closed sbmadhav closed 6 years ago
After quick analysis, Current status of master:
443 errors, 2 warnings
155 errors fixable with the eslint --fix
option
121 Unexpected tab character issues 51 Mixed spaces and tabs 19 missing in props validation 19 no-unused-vars 17 indent issues
and so on.
An easy, yet tedious task. I am currently unable to pick this up, but if no one picks it up, I will in coming days.
Also, my prior experience makes me believe enforcing git hooks through a tool like husky would eliminate badly linted code getting inside master.
ESLint error resolved including githooks https://github.com/pagesource/fusion-components/pull/66
@sbmadhav @areai51 can we close this issue as #66 is merged?
@vinaymavi - I still see eslint errors in development branch. Were all error resolved?
yes @sbmadhav i have fixed all eslint errors manually. please checkout development branch at commit hash b3583860ff1f10e558fab622175d76c79a843787 and try npm run lint this should display only single warning over here.
It looks like some thing went wrong with repository that we need to investigate.
Do you want to request a feature or report a bug? Bug What is the current behavior? Multiple eslint errors. (excerpt below) What is the expected behavior? No eslint errors.
Below are the errors that need to be fixed-