[FIX] linting scripts for lintstaged

[surchs]

• Closes Linting scripts are not correctly setup for lintstaged #590

Changes proposed in this pull request:

• Create separate scripts for single file (:file and global runs)
• we could also hard-code the script in lintstaged - but then it's harder to keep them in sync

Checklist

This section is for the PR reviewer

• PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
• PR has a label for the release changelog or skip-release (to be applied by maintainers only)
• PR links to GitHub issue with mention Closes #XXXX
• Tests pass
• Checks pass
• If the PR changes the participant-level and/or the dataset-level result file, the query-tool-results files in the neurobagel_examples repo have been regenerated

For new features:

• Tests have been added

For bug fixes:

• There is at least one test that would fail under the original bug conditions.

Summary by Sourcery

Fix and enhance linting and formatting scripts by introducing separate file-scoped commands and updating lint-staged configuration

Bug Fixes:

• Fix lint:check and lint:fix scripts to correctly target files in lint-staged

Enhancements:

• Add dedicated file-scoped npm scripts for lint:check:file, lint:fix:file, format:check:file, and format:fix:file
• Update root-level lint:check, lint:fix, format:check, and format:fix commands to explicitly include project directory

Chores:

• Align .lintstagedrc.json to use the new file-scoped scripts

[netlify]

✅ Deploy Preview for neurobagel-query ready!

Name	Link
🔨 Latest commit	d1da6c4
🔍 Latest deploy log	https://app.netlify.com/projects/neurobagel-query/deploys/6883929be8c3d800089596a2
😎 Deploy Preview	https://deploy-preview-591--neurobagel-query.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sourcery-ai]

Reviewer's Guide

Separated linting and formatting scripts into file-scoped and global variants and updated lint-staged configuration to leverage the new file-level commands for staged files.

File-Level Changes

Change	Details	Files
Split lint and format scripts into file-scoped and global commands	Added lint:check:file and lint:fix:file scripts without a target path for single-file runs Updated lint:check and lint:fix to explicitly include “.” for project-wide runs Introduced format:fix:file and format:check:file for per-file formatting Adjusted format:fix and format:check to target project root with “.”	package.json
Updated lint-staged to use new file-scoped scripts	Changed ts/tsx lint-staged entries to invoke lint:check:file and lint:fix:file Updated formatting tasks to call format:check:file and format:fix:file	.lintstagedrc.json

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#590	Update linting and formatting scripts in package.json so that when run via lint-staged, they only operate on staged files (not the entire repo).	✅
#590	Ensure that global scripts (for running on the entire repo) and per-file scripts (for lint-staged) are both available and appropriately separated.	✅
#590	Remove the use of the '.' context from scripts intended for lint-staged, so that lint-staged can pass the list of staged files directly.	✅

Possibly linked issues

• Linting scripts are not correctly setup for lintstaged #590: The PR fixes the issue by creating dedicated file-level linting scripts, ensuring lintstaged only processes staged files.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine

[rmanaem]

Thanks for the PR @surchs! 🧑‍🍳
P.S. don't forget the PR label

[neurobagel-bot]

🚀 PR was released in v0.11.0 🚀