Skip to content

Eslint changes#77

Open
Tejas-ChandraShekarRaju wants to merge 5 commits intoRealDevSquad:developfrom
Tejas-ChandraShekarRaju:eslintChanges
Open

Eslint changes#77
Tejas-ChandraShekarRaju wants to merge 5 commits intoRealDevSquad:developfrom
Tejas-ChandraShekarRaju:eslintChanges

Conversation

@Tejas-ChandraShekarRaju
Copy link
Copy Markdown
Contributor

Description

  1. Switched off react/react-in-jsx-scopesince its no longer needed from react 17
  2. Switched off react/prop-types since we are not using types
  3. Ran prettier
  4. Changed file extension from .eslintrc to .eslintrc.js

Fixes # (issue)
Build was failing because of wrong extension. .eslintrc couldn't detect module.exports hence changed extension to .eslintrc.js

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Manual Testing

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

…om react 17 2. Switched off react/prop-types since we are not using types 3. Ran prettier 4. Changed file extension from .eslintrc to .eslintrc.js
Comment thread ui/package-lock.json
},
"eslint-webpack-plugin": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/eslint-webpack-plugin/-/eslint-webpack-plugin-3.1.1.tgz",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you check why this has been updated?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DeRaowl Changed to parser: "@babel/eslint-parser" from parser: "@babel/eslint". For this I've added the dependency in package.json. Hence the update in package-lock.json


})

it("Should fire event on click ascending", async () => {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why test related to fireEvent removed?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @DeRaowl we moved this click event from the cursor to the header. So we have to implement tests for the header

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