Fix JavaScript lint errors

Aperta
#16,201 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@wanjinhao1 ci sta già lavorando.

Dal 17/10/2026.

  • #16202 di @wanjinhao1 — aperta

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
javascript
Ambito
tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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>".
Lingua principale
JavaScript
Stelle
6k
Fork
1.3k
Merge medio
1g 21h
PR unite (30g)
224

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stdlib-js/stdlib

Tutte le issue di stdlib-js/stdlib

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.