Skip to content

chore: fix EditorConfig lint errors (issue #11326)#11328

Open
GuneetGill wants to merge 1 commit intostdlib-js:developfrom
GuneetGill:chore/fix-editorconfig-lint-11326
Open

chore: fix EditorConfig lint errors (issue #11326)#11328
GuneetGill wants to merge 1 commit intostdlib-js:developfrom
GuneetGill:chore/fix-editorconfig-lint-11326

Conversation

@GuneetGill
Copy link
Copy Markdown

Description

What is the purpose of this pull request?

This pull request:

  • Fixes EditorConfig lint failures reported in the automated workflow by aligning two files with .editorconfig rules.
  • Replaces tab indentation with two-space indentation in lib/node_modules/@stdlib/_tools/lint/pkg-json/test/fixtures/invalid.json (JSON fixtures use spaces; the file remains intentionally invalid JSON for tests).
  • Replaces space indentation with tab indentation inside the sample-output block comments in lib/node_modules/@stdlib/ndarray/to-fancy/examples/set_slice.3d.js (JavaScript uses tabs).

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

Disclosure

I asked Claude to explain the codebase and what files to modify.


@stdlib-js/reviewers

@stdlib-bot stdlib-bot added First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. Good First PR A pull request resolving a Good First Issue. labels Apr 8, 2026
@github-actions github-actions bot mentioned this pull request Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Good First PR A pull request resolving a Good First Issue. Needs Review A pull request which needs code review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants