chore(deps): update dependency eslint-config-galex to v4.5.2

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-galex	4.1.9 -> 4.5.2

---

Release Notes

ljosberinn/eslint-config-galex (eslint-config-galex)

v4.5.2

Compare Source

Bug Fixes

• deps: revert engines field back to 14.17 (0e7554a)

• decrease semantic-relase to 19.0.5
• fix(deps): update dependency eslint-import-resolver-typescript to v3.5.4
• chore(deps): update dependency eslint to v8.37.0
• fix(deps): update dependency eslint-plugin-tailwindcss to v3.10.3
• chore(deps): update dependency semantic-release to v21.0.1
• fix(deps): update dependency @​babel/core to v7.21.4
• fix(deps): update dependency typescript to v5.0.3

v4.5.1

Compare Source

Bug Fixes

• actually enable tailwind css plugin (e315efd)

v4.5.0

Compare Source

Features

• deps: adopt eslint-plugin-simple-import-sort (532a305), closes #​744
• deps: adopt eslint-plugin-tailwindcss (1f8fcd4)
• deps: update deps. bump req. node version to 18.12 (LTS) (080eb44)

• disable import/sort

• disable @typescript-eslint/consistent-type-imports for tests

• self lint & autofix

• closes https://github.com/ljosberinn/eslint-config-galex/issues/744

• deprecate react/jsx-sort-default-props

• use react/sort-default-props (off)

• add react-no-object-type-as-default-prop (error)

• add jsx-a11y/prefer-tag-over-role (error)

• add jsx-a11y/no-aria-hidden-on-focusable (error)

• add import/consistent-type-specifier-style (warn, autofixable)

• add import/no-empty-named-blocks (warn, autofixable)

• enable @typescript-eslint-prefer-nullish-coalescing only if compilerOptions.strictNullChecks is active

v4.4.2

Compare Source

Bug Fixes

• deps: update dependency @​babel/core to v7.20.12 (#​725) (b119bc8)

v4.4.1

Compare Source

Bug Fixes

• deps: update dependency eslint-plugin-jest to v27.2.0 (2b0e074)
• deps: update dependency eslint-plugin-react to v7.31.11 (1bfe9e2)
• deps: update dependency eslint-plugin-sonarjs to v0.17.0 (b46d5b5)
• deps: update dependency eslint-plugin-storybook to v0.6.8 (586967c)
• deps: update dependency eslint-plugin-unicorn to v45 (498395f)
• deps: update dependency typescript to v4.9.4 (40ef897)

v4.4.0

Compare Source

Features

• deps: add eslint-plugin-etc (bf08daf), closes #​593

v4.3.2

Compare Source

Bug Fixes

• deps: update dependency eslint to v8.27.0 (a886a43)
• deps: update dependency eslint-import-resolver-typescript to v3.5.2 (0b8075c)
• deps: update dependency eslint-plugin-jest to v27.1.5 (2a2e4ae)
• deps: update dependency eslint-plugin-jest-dom to v4.0.3 (7c5bde1)
• deps: update dependency eslint-plugin-promise to v6.1.1 (c959fd9)
• deps: update dependency eslint-plugin-storybook to v0.6.7 (8439f8a)
• deps: update dependency eslint-plugin-testing-library to v5.9.1 (082983d)
• deps: update nextjs monorepo to v13 (major) (4d523aa)
• deps: update typescript-eslint monorepo to v5.42.1 (4540cda)

v4.3.1

Compare Source

Bug Fixes

• actually update eslint-plugin-jest (4d1b873)
• deps: update dependency eslint-plugin-unicorn to v44 (d004c8e)

v4.3.0

Compare Source

Bug Fixes

• deps: update dependency eslint to v8.25.0 (6335331)
• deps: update nextjs monorepo to v12.3.1 (7710a8b)

Features

• deps: update dependency eslint to v8.25.0 (218f1d3)

v4.2.2

Compare Source

Bug Fixes

• deps: update dependencies (13c2a3f)

v4.2.1

Compare Source

Bug Fixes

• enable es6 env (458b3b5)

v4.2.0

Compare Source

Features

• add enableJavaScriptSpecificRulesInTypeScriptProject createConfig argument (309c7a4)

---

Configuration

📅 Schedule: Branch creation - "every month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.