You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up issue for #2272 (where it is suggested to open a new issue).
Is your feature request related to a problem? Please describe.
Some parts of the mock data generation process use their own source of randomness and are difficult to work around. Specifically the generation of enum values.
Describe the solution you'd like
The API could accept a function that returns a random value which is used instead of Math.random(). That would allow the user to make the default behavior deterministic.
Describe alternatives you've considered
Providing custom data generators for every enum type. It's impractical for larger schemas and tedious to account for schema changes.
Generators for enum values could themselves be generated with a custom codgen plugin, but that also requires an understanding of the codegen process.
The text was updated successfully, but these errors were encountered:
This is a follow up issue for #2272 (where it is suggested to open a new issue).
Is your feature request related to a problem? Please describe.
Some parts of the mock data generation process use their own source of randomness and are difficult to work around. Specifically the generation of enum values.
Describe the solution you'd like
The API could accept a function that returns a random value which is used instead of Math.random(). That would allow the user to make the default behavior deterministic.
Describe alternatives you've considered
Providing custom data generators for every enum type. It's impractical for larger schemas and tedious to account for schema changes.
Generators for enum values could themselves be generated with a custom codgen plugin, but that also requires an understanding of the codegen process.
The text was updated successfully, but these errors were encountered: