Skip to content

Conversation

@katarinazaprazna
Copy link
Collaborator

@katarinazaprazna katarinazaprazna commented Oct 24, 2025

Description

Planning to merge after RHINENG-18569 to prevent merge conflicts.

Configuration Alignment

  • I've unified the development configuration to match the content-sources-frontend repository for easier maintenance across both projects
  • Prettier was added and configured to handle all code formatting, allowing ESLint to focus strictly on code quality rules alone. This change allowed us to remove the redundant EditorConfig file and clean up /* global ... */ comments by moving environment settings into the main ESLint file

Tool Modernization and Scope

  • ESLint was bumped from v7 to v9 (Flat Config Format)
  • For styles, Prettier now handles SCSS formatting, and Stylelint handles SCSS quality rules
  • I narrowed ESLint's scope to only lint the /src directory, excluding the /config folder to prevent issues with older conventions

Git

  • Adjusted commitlint config to enforce the 50/72 rule for commit message formatting, aligning with the content-sources-frontend repository

How to test the PR

  • Verify that the app builds without any errors.
  • Ensure that all automated tests pass.
  • Ensure that output of running npm run lint:js:fix, npm run lint:sass and npm run prettier:check will be a message confirming that all linting and formatting rules have been satisfied.

Checklist:

  • The commit message has the Jira ticket linked
  • PR has a short description
  • Screenshots before and after the change are added
  • Tests for the changes have been added
  • README.md is updated if necessary
  • Needs additional dependent work

Copy link
Contributor

@TenSt TenSt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@katarinazaprazna katarinazaprazna force-pushed the unify-linting-and-formatting-configs branch from 87187a6 to dfdd7b9 Compare November 1, 2025 19:34
@katarinazaprazna katarinazaprazna marked this pull request as ready for review November 1, 2025 19:35
@katarinazaprazna katarinazaprazna requested a review from a team as a code owner November 1, 2025 19:35
@codecov-commenter
Copy link

codecov-commenter commented Nov 1, 2025

Codecov Report

❌ Patch coverage is 53.28244% with 612 lines in your changes missing coverage. Please review.
✅ Project coverage is 62.36%. Comparing base (2511619) to head (575daa5).

Files with missing lines Patch % Lines
...c/SmartComponents/PatchSetDetail/PatchSetDetail.js 0.00% 107 Missing and 13 partials ⚠️
src/SmartComponents/PatchSet/PatchSet.js 0.00% 63 Missing and 2 partials ⚠️
...rtComponents/PatchSetWizard/steps/ReviewSystems.js 0.00% 47 Missing and 4 partials ⚠️
...rc/SmartComponents/SystemDetail/InventoryDetail.js 0.00% 24 Missing and 3 partials ⚠️
src/Routes.js 0.00% 24 Missing and 2 partials ⚠️
src/SmartComponents/Modals/AssignSystemsModal.js 50.00% 23 Missing ⚠️
...c/SmartComponents/PatchSetWizard/PatchSetWizard.js 0.00% 18 Missing and 3 partials ⚠️
src/App.js 0.00% 15 Missing and 3 partials ⚠️
...c/SmartComponents/PackageSystems/PackageSystems.js 68.42% 15 Missing and 3 partials ⚠️
src/SmartComponents/PatchSetWizard/WizardAssets.js 39.28% 12 Missing and 5 partials ⚠️
... and 40 more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1420      +/-   ##
==========================================
- Coverage   62.93%   62.36%   -0.57%     
==========================================
  Files         128      128              
  Lines        3399     3329      -70     
  Branches      906      901       -5     
==========================================
- Hits         2139     2076      -63     
+ Misses       1141     1132       -9     
- Partials      119      121       +2     

☔ 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.

@katarinazaprazna katarinazaprazna force-pushed the unify-linting-and-formatting-configs branch 2 times, most recently from 04874c3 to ae2c4cf Compare November 3, 2025 14:27
Unifying configs across the Patch and content-sources-frontend
repositories. Patch now uses Prettier for formatting and ESLint for
quality rules only. ESLint has also been upgraded to v9.
Adjust the commitlint config to use the 50/72 rule similarly to the
content-sources-frontend repository
This commit enforces the `import/no-duplicates` rule in ESLint with
auto-fix enabled.
@katarinazaprazna katarinazaprazna force-pushed the unify-linting-and-formatting-configs branch from ae2c4cf to 575daa5 Compare November 4, 2025 14:26
@katarinazaprazna katarinazaprazna merged commit d1d2aae into RedHatInsights:master Nov 4, 2025
3 of 4 checks passed
@sentry
Copy link

sentry bot commented Nov 5, 2025

Issues attributed to commits in this pull request

This pull request was merged and Sentry observed the following issues:

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants