Fix JavaScript lint errors

Ouverte
#16,201 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@wanjinhao1 y travaille déjà.

Depuis le 17/10/2026.

  • #16202 par @wanjinhao1 — ouverte

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
15/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
javascript
Domaine
tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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>".
Langage dominant
JavaScript
Étoiles
6k
Forks
1.3k
Merge moyen
1 j 21 h
PR mergées (30 j)
224

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de stdlib-js/stdlib

Toutes les issues de stdlib-js/stdlib

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.