Skip to content

Document new factoryCreateQuietly response generation method #35

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.

Sign up for GitHub

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

Open
J-T-McC wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document new factoryCreateQuietly response generation method #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions laravel/documenting/60-responses.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -753,6 +753,11 @@ You can customise this process in a few ways:
### Changing the strategies
You can change the order of these strategies, or remove the ones you don't need by editing the `examples.models_source` config item. By default, it's set to `['factoryCreate', 'factoryMake', 'databaseFirst']`, corresponding to the three main strategies above.


:::note
`factoryCreate` will dispatch model events resulting in listener execution which could negatively impact generation time in large event driven projects. `factoryCreateQuietly` can be used to suppress model events if they are not a requirement for your generated data.
:::

### Applying states
If you want specific [states](https://laravel.com/docs/database-testing#factory-states) to be applied to your model factory, you can use the `states` field on `@apiResourceModel` or `@transformerModel`. Separate multiple states with a comma. If you're using attributes, use the `factoryStates:` argument with an array of states.

Expand Down