-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix ESLint errors for eventhub packages #10777
Labels
Client
This issue points to a problem in the data-plane of the library.
Event Hubs
help wanted
This issue is tracking work for which community contributions would be welcomed and appreciated
Milestone
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Aug 23, 2020
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Aug 25, 2020
ramya-rao-a
added
Client
This issue points to a problem in the data-plane of the library.
Event Hubs
labels
Aug 25, 2020
ramya-rao-a
added
help wanted
This issue is tracking work for which community contributions would be welcomed and appreciated
and removed
Up for grabs
labels
Sep 15, 2020
ghost
pushed a commit
that referenced
this issue
Jan 21, 2021
Round 1 addressing #10777 Replaces #13013 This leaves 5 errors and 15 warnings (excluding TSDoc) after this PR is merged. - 4 'Promise executor functions should not be async' errors. Fixing this will take a lot of care and I would want these to be reviewed on their own so they don't get lost in the noise. - 1 'N is already defined'. This is due to a constant matching an interface name.
ljian3377
pushed a commit
to ljian3377/azure-sdk-for-js
that referenced
this issue
Jan 22, 2021
Round 1 addressing Azure#10777 Replaces Azure#13013 This leaves 5 errors and 15 warnings (excluding TSDoc) after this PR is merged. - 4 'Promise executor functions should not be async' errors. Fixing this will take a lot of care and I would want these to be reviewed on their own so they don't get lost in the noise. - 1 'N is already defined'. This is due to a constant matching an interface name.
This was referenced Feb 11, 2021
This was referenced Feb 22, 2021
The |
ghost
pushed a commit
that referenced
this issue
Feb 22, 2021
Fixes the last error in Event Hubs package and allows future linter errors to break the build. We need to fix up the checkpoint store package before we can close the related issue #10777
ghost
pushed a commit
that referenced
this issue
Apr 2, 2021
Resolves #10777 by addressing the last outstanding item. With this change, `@azure/eventhubs-checkpointstore-blob` now no longer has eslint errors.
jay-most
pushed a commit
to jay-most/azure-sdk-for-js
that referenced
this issue
Apr 26, 2021
Resolves Azure#10777 by addressing the last outstanding item. With this change, `@azure/eventhubs-checkpointstore-blob` now no longer has eslint errors.
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Client
This issue points to a problem in the data-plane of the library.
Event Hubs
help wanted
This issue is tracking work for which community contributions would be welcomed and appreciated
Fix lint errors found in eventhub packages by ESLint. Following are the steps to run ESLint for eventhub packages and reproduce this issue.
<repo root>/sdk/eventhub/<package-name>
rushx lint
<repo root>/sdk/eventhub/<package-name>
with name ends with lintReport.htmlOnce all known issues are resolved, below change is required in
package.json
file in package root<repo root>/sdk/eventhub/<package-name>
to treat any new lint regression as hard failure in CI.package.json
-f html -o template-lintReport.html || exit 0
Note: HTML report name prefix may be different for each package name to differentiate the report for each package.
The text was updated successfully, but these errors were encountered: