π·οΈ Better typings for constant
#4999
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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 9864176:
|
Codecov ReportAll modified and coverable lines are covered by tests β
Additional details and impacted files@@ Coverage Diff @@
## next-3_18_0 #4999 +/- ##
============================================
Coverage 96.73% 96.73%
============================================
Files 213 213
Lines 16252 16252
Branches 2652 2652
============================================
Hits 15721 15721
Misses 531 531
Flags with carried forward coverage won't be shown. Click here to find out more. β View full report in Codecov by Sentry. |
|
π A preview of the new documentation is available at: http://664c462f56a6519ceb08f739--dubzzz-fast-check.netlify.app |
dubzzz
commented
May 21, 2024
| @@ -119,7 +119,7 @@ describe('webUrl (integration)', () => { | |||
| function webUrlConstraintsBuilder(onlySmall?: boolean): fc.Arbitrary<WebUrlConstraints> { | |||
| return fc.record( | |||
| { | |||
| validSchemes: fc.constant(['ftp']), | |||
| validSchemes: fc.constant<string[]>(['ftp']), | |||
dubzzz
added a commit
that referenced
this pull request
May 29, 2024
**Description** As recommended by #4047, let's leverage const generics to make usage of `constant` even simpler for TS users. Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs. <!-- Please provide a short description and potentially linked issues hustifying the need for this PR --> <!-- * 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: π·οΈ Add or update types - [x] Impacts: Typings <!-- [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? -->
dubzzz
added a commit
that referenced
this pull request
Jul 16, 2024
**Description** As recommended by #4047, let's leverage const generics to make usage of `constant` even simpler for TS users. Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs. <!-- Please provide a short description and potentially linked issues hustifying the need for this PR --> <!-- * 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: π·οΈ Add or update types - [x] Impacts: Typings <!-- [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? -->
dubzzz
added a commit
that referenced
this pull request
Aug 13, 2024
**Description** As recommended by #4047, let's leverage const generics to make usage of `constant` even simpler for TS users. Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs. <!-- Please provide a short description and potentially linked issues hustifying the need for this PR --> <!-- * 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: π·οΈ Add or update types - [x] Impacts: Typings <!-- [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? -->
dubzzz
added a commit
that referenced
this pull request
Sep 23, 2024
**Description** As recommended by #4047, let's leverage const generics to make usage of `constant` even simpler for TS users. Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs. <!-- Please provide a short description and potentially linked issues hustifying the need for this PR --> <!-- * 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: π·οΈ Add or update types - [x] Impacts: Typings <!-- [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? -->
dubzzz
added a commit
that referenced
this pull request
Nov 6, 2024
**Description** As recommended by #4047, let's leverage const generics to make usage of `constant` even simpler for TS users. Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs. <!-- Please provide a short description and potentially linked issues hustifying the need for this PR --> <!-- * 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: π·οΈ Add or update types - [x] Impacts: Typings <!-- [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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As recommended by #4047, let's leverage const generics to make usage of
constanteven simpler for TS users.Not really a breaking change on its own but given we play with types and change the way we declare some, let's be safe and pack this change with other "next major" devs.
Checklist β Don't delete this checklist and make sure you do the following before opening the PR
yarn bumpand flag the impacts properlyAdvanced