Skip to content

Update to yarn equivalent for linting#11531

Open
epugh wants to merge 2 commits intoopensearch-project:mainfrom
o19s:update-lint-directions
Open

Update to yarn equivalent for linting#11531
epugh wants to merge 2 commits intoopensearch-project:mainfrom
o19s:update-lint-directions

Conversation

@epugh
Copy link
Contributor

@epugh epugh commented Mar 16, 2026

Description

Update Developer Guide for how to lint code using yarn.

Issues Resolved

n/a

Screenshot

Testing the changes

Run the suggested command! I scanned the rest of the DEVELOPER_GUIDE.md and didn't see any other uses of node that should be converted to yarn.

Changelog

doc: Update lint instructions to use yarn

Check List

  • All tests pass
    • yarn test:jest
    • yarn test:jest_integration
  • New functionality includes testing.
  • New functionality has been documented.
  • Update CHANGELOG.md
  • Commits are signed per the DCO using --signoff

Signed-off-by: Eric Pugh <epugh@opensourceconnections.com>
@github-actions
Copy link
Contributor

❌ Changelog Entry Missing Hyphen

Changelog entries must begin with a hyphen (-).

@github-actions
Copy link
Contributor

github-actions bot commented Mar 16, 2026

PR Reviewer Guide 🔍

(Review updated until commit 61de8ca)

Here are some key observations to aid the review process:

🧪 No relevant tests
🔒 No security concerns identified
✅ No TODO sections
🔀 No multiple PR themes
⚡ Recommended focus areas for review

Command Accuracy

The new lint command yarn run lint:es --fix && yarn run lint:style --fix should be verified to ensure both scripts exist in package.json and that this is the recommended/complete way to run linting. It's worth confirming whether yarn lint or another shorthand exists that might be simpler to document.

can run `yarn run lint:es --fix && yarn run lint:style --fix` to fix linting issues and apply Prettier formatting.

@github-actions
Copy link
Contributor

❌ Changelog Entry Missing Hyphen

Changelog entries must begin with a hyphen (-).

Signed-off-by: Eric Pugh <epugh@opensourceconnections.com>
@github-actions
Copy link
Contributor

Persistent review updated to latest commit 61de8ca

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.47%. Comparing base (68ee497) to head (61de8ca).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11531      +/-   ##
==========================================
+ Coverage   61.01%   61.47%   +0.46%     
==========================================
  Files        4990     4988       -2     
  Lines      137539   136533    -1006     
  Branches    24104    23602     -502     
==========================================
+ Hits        83916    83934      +18     
+ Misses      47564    46567     -997     
+ Partials     6059     6032      -27     
Flag Coverage Δ
Linux_1 25.04% <ø> (+0.26%) ⬆️
Linux_2 39.36% <ø> (+<0.01%) ⬆️
Linux_3 42.57% <ø> (+0.02%) ⬆️
Linux_4 33.85% <ø> (+0.35%) ⬆️
Windows_1 25.06% <ø> (+0.26%) ⬆️
Windows_2 39.33% <ø> (+<0.01%) ⬆️
Windows_3 42.58% <ø> (+0.02%) ⬆️
Windows_4 33.85% <ø> (+0.35%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant