Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

♻️ Switch to object spreading rather than Object.assign #5300

Merged
merged 1 commit into from
Sep 27, 2024

Conversation

dubzzz
Copy link
Owner

@dubzzz dubzzz commented Sep 27, 2024

Description

As we dropped support for versions of Node not supporting object spreading we can now use it barely everywhere needed.

Fix #5299

ChecklistDon't delete this checklist and make sure you do the following before opening the PR

  • The name of my PR follows gitmoji specification
  • My PR references one of several related issues (if any)
    • New features or breaking changes must come with an associated Issue or Discussion
    • My PR does not add any new dependency without an associated Issue or Discussion
  • My PR includes bumps details, please run yarn bump and flag the impacts properly
  • My PR adds relevant tests and they would have failed without my PR (when applicable)

Advanced

  • Category: Refactoring
  • Impacts: Force users to rely on more modern versions of Node

As we dropped support for versions of Node not supporting object spreading we can now use it barely everywhere needed.

Fix #5299
Copy link

changeset-bot bot commented Sep 27, 2024

⚠️ No Changeset found

Latest commit: d81eecd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dubzzz dubzzz enabled auto-merge (squash) September 27, 2024 20:33
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d81eecd:

Sandbox Source
@fast-check/examples Configuration

Copy link
Contributor

👋 A preview of the new documentation is available at: http://66f7174e90b096e829dcf03b--dubzzz-fast-check.netlify.app

Copy link

codecov bot commented Sep 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.05%. Comparing base (5c94bd9) to head (d81eecd).
Report is 1 commits behind head on next-3_22_0.

Additional details and impacted files
@@               Coverage Diff               @@
##           next-3_22_0    #5300      +/-   ##
===============================================
- Coverage        95.05%   95.05%   -0.01%     
===============================================
  Files              221      221              
  Lines            10058    10052       -6     
  Branches          2634     2634              
===============================================
- Hits              9561     9555       -6     
  Misses             497      497              
Flag Coverage Δ
unit-tests 95.05% <100.00%> (-0.01%) ⬇️
unit-tests-18.x-Linux 95.05% <100.00%> (-0.01%) ⬇️
unit-tests-20.x-Linux 95.05% <100.00%> (-0.01%) ⬇️
unit-tests-22.x-Linux 95.05% <100.00%> (-0.01%) ⬇️
unit-tests-latest-Linux 95.05% <100.00%> (-0.01%) ⬇️

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.

@dubzzz dubzzz merged commit 15fa6d0 into next-3_22_0 Sep 27, 2024
55 checks passed
@dubzzz dubzzz deleted the drop-dead-assign branch September 27, 2024 20:40
dubzzz added a commit that referenced this pull request Nov 6, 2024
**Description**

<!-- Please provide a short description and potentially linked issues
justifying the need for this PR -->

As we dropped support for versions of Node not supporting object
spreading we can now use it barely everywhere needed.

Fix #5299

<!-- * Your PR is fixing a bug or regression? Check for existing issues
related to this bug and link them -->
<!-- * Your PR is adding a new feature? Make sure there is a related
issue or discussion attached to it -->

<!-- You can provide any additional context to help into understanding
what's this PR is attempting to solve: reproduction of a bug, code
snippets... -->

**Checklist** — _Don't delete this checklist and make sure you do the
following before opening the PR_

- [x] The name of my PR follows [gitmoji](https://gitmoji.dev/)
specification
- [x] My PR references one of several related issues (if any)
- [x] New features or breaking changes must come with an associated
Issue or Discussion
- [x] My PR does not add any new dependency without an associated Issue
or Discussion
- [x] My PR includes bumps details, please run `yarn bump` and flag the
impacts properly
- [x] My PR adds relevant tests and they would have failed without my PR
(when applicable)

<!-- More about contributing at
https://github.com/dubzzz/fast-check/blob/main/CONTRIBUTING.md -->

**Advanced**

<!-- How to fill the advanced section is detailed below! -->

- [x] Category: Refactoring
- [x] Impacts: Force users to rely on more modern versions of Node

<!-- [Category] Please use one of the categories below, it will help us
into better understanding the urgency of the PR -->
<!-- * ✨ Introduce new features -->
<!-- * 📝 Add or update documentation -->
<!-- * ✅ Add or update tests -->
<!-- * 🐛 Fix a bug -->
<!-- * 🏷️ Add or update types -->
<!-- * ⚡️ Improve performance -->
<!-- * _Other(s):_ ... -->

<!-- [Impacts] Please provide a comma separated list of the potential
impacts that might be introduced by this change -->
<!-- * Generated values: Can your change impact any of the existing
generators in terms of generated values, if so which ones? when? -->
<!-- * Shrink values: Can your change impact any of the existing
generators in terms of shrink values, if so which ones? when? -->
<!-- * Performance: Can it require some typings changes on user side?
Please give more details -->
<!-- * Typings: Is there a potential performance impact? In which cases?
-->
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.

1 participant