Fix JavaScript lint errors

Offen
#16,201 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@wanjinhao1 arbeitet bereits daran.

Seit 17.10.2026.

  • #16202 von @wanjinhao1 — offen

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
15/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
javascript
Bereich
tooling

Rechercherichtung

Read lib/node_modules/@stdlib/string/base/percent-encode/lib/main.js at the reported lint location, line 91, and compare its usage with the suggested @stdlib/string/uppercase or @stdlib/string/base/uppercase APIs. Confirm the lint failure is resolved by rerunning the JavaScript lint workflow; the issue is already being addressed by linked pull request #16202.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Good First Issue

JavaScript Linting Failures

Linting failures were detected in the automated JavaScript lint workflow run.

Workflow Details
Error Details
make[1]: Entering directory '/home/runner/work/stdlib/stdlib'

Linting file: lib/node_modules/@stdlib/blas/ext/base/ndarray/saxpb/lib/main.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/gamma/kurtosis/lib/index.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/cosine/logcdf/lib/main.js

Linting file: lib/node_modules/@stdlib/math/base/special/absgammalnf/lib/native.js

Linting file: lib/node_modules/@stdlib/streams/node/transform/lib/destroy.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/hypergeometric/mode/lib/index.js

Linting file: lib/node_modules/@stdlib/_tools/package-json/standardize/lib/main.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/laplace/stdev/lib/native.js

Linting file: lib/node_modules/@stdlib/lapack/base/dlarf/lib/main.js

Linting file: lib/node_modules/@stdlib/stats/array/rangeabs/lib/main.js

Linting file: lib/node_modules/@stdlib/ndarray/base/any-by/lib/7d_accessors.js

Linting file: lib/node_modules/@stdlib/stats/strided/dmskmin/lib/dmskmin.native.js

Linting file: lib/node_modules/@stdlib/math/base/special/haversin/lib/native.js

Linting file: lib/node_modules/@stdlib/number/int32/base/mul/lib/main.js

Linting file: lib/node_modules/@stdlib/ndarray/base/unary/lib/nd_accessors.js

Linting file: lib/node_modules/@stdlib/fs/resolve-parent-path/lib/validate.js

Linting file: lib/node_modules/@stdlib/strided/base/binary/lib/ndarray.js

Linting file: lib/node_modules/@stdlib/strided/base/smskmap/lib/ndarray.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/laplace/entropy/lib/index.js

Linting file: lib/node_modules/@stdlib/math/base/special/polygamma/lib/native.js

Linting file: lib/node_modules/@stdlib/namespace/lib/namespace/random/main.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/zxsy/lib/ndarray.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/dcunone/lib/dcunone.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/dnansumpw/lib/native.js

Linting file: lib/node_modules/@stdlib/string/base/percent-encode/lib/main.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/string/base/percent-encode/lib/main.js
91:17  error  Use `@stdlib/string/uppercase` or `@stdlib/string/base/uppercase` instead of String.prototype.toUpperCase  no-restricted-syntax

✖ 1 problem (1 error, 0 warnings)

Linting failed.
make[1]: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/eslint.mk:261: eslint-files] Error 1
make[1]: Leaving directory '/home/runner/work/stdlib/stdlib'
make: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/Makefile:158: lint-javascript-files] Error 2
Pull Request Instructions
  • Please use the following PR title format:
    "chore: fix JavaScript lint errors (issue #<ISSUE_NUMBER>)".
  • Reference this issue in the "Related Issues" section of the PR body as "resolves #<ISSUE_NUMBER>".
Vorherrschende Sprache
JavaScript
Sterne
6k
Forks
1.3k
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
224

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus stdlib-js/stdlib

Alle Issues in stdlib-js/stdlib

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.