Skip to content

Conversation

shubham1172
Copy link
Member

Description

Per #184, we stopped redirecting npm run lint to /dev/null. This PR fixes some existing linting issues.

Issue reference

Please reference the issue this PR will close: #188

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests (NA
  • Extended the documentation (NA)

Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
@shubham1172 shubham1172 requested review from a team as code owners February 16, 2022 07:19
@shubham1172 shubham1172 changed the title Resolve linter issues [WIP] Resolve linter issues Feb 16, 2022
@shubham1172
Copy link
Member Author

shubham1172 commented Feb 16, 2022

@XavierGeerinck / @amulyavarote, should we enforce linting, going forward?

Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
@shubham1172 shubham1172 changed the title [WIP] Resolve linter issues Resolve linter issues Feb 16, 2022
Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
@shubham1172
Copy link
Member Author

/cc @XavierGeerinck for review

@XavierGeerinck
Copy link
Contributor

LGTM

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.

Resolve linting issues
2 participants