Nicolas DUBIEN

## 💡 Idea While not critical, in some cases it might be simpler to have a built-in way to wait for the next task to be scheduled (without releasing anything...

## 💡 Idea Probably attach the name of the PRNG to the state and find a way to find the PRNG from its name Follow-up for https://github.com/dubzzz/fast-check/pull/4063

We will have to ask ourselves if it should start release on schedule, or wait next micro task, or wait next delay...

## Description du talk * Titre : React Server Components, quèsaco?! * Contenu (Décrivez brièvement le contenu de la présentation) : Les React Server Components commencent à faire parler d'eux...

BREAKING CHANGE: Moving to latest version of `@typescript-eslint/utils`

1

Not being on the latest version of `@typescript-eslint/utils` prevents users to easily move to the v9 of eslint. By moving away from `@typescript-eslint/experimental-utils` and replacing it by its modern package...

✨ Add ability to limit shrink path

3

**Description** We want to offer a way for our users to limit the depth and overall size of the shrinking capabilities. At the moment, they can only either apply shrink...

## 💡 Idea Have a look to isolatedDeclarations with the new versions of TypeScript

Provide a built-in way to generate set of entities having relationships between each others

1

## 💡 Idea Generating structures being tied to one another in a many-to-many or one-to-many relationship in fast-check is not trivial. While feasible it requires our users to come up...

## 🚀 Feature Request ## Motivation There is no need for our arbitraries to require non-readonly options. They should be ok with receiving readonly versions of their constraints. Needed for...

## 🚀 Feature Request At the moment `fc.record` only produce editable (aka writable) instances. In reality it could mirror what the user passed to it. If the received model is...