Skip to content

Commit

Permalink
Merge branch 'main' into feat/rsc-build
Browse files Browse the repository at this point in the history
  • Loading branch information
dac09 committed Feb 19, 2024
2 parents 5e767b2 + cf3c421 commit 7ff0461
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
6 changes: 0 additions & 6 deletions docs/docs/mailer.md
Original file line number Diff line number Diff line change
Expand Up @@ -274,12 +274,6 @@ You can have a preview of what your mail templates will look like. These will re

When running in development mode, using the default `@redwoodjs/mailer-handler-studio` development handler, your mail will be sent to a local SMTP inbox running inside of Studio. This allows you to use your app and have full emails sent without worrying about setting up a local inbox yourself or using some other online temporary inbox service.

:::warning

Redwood Studio is an experimental feature and is still in development. Some of the UI shown above might look slightly different and the functionality may be tweaked over time to provide you with a better experience.

:::

## Need a Renderer or Handler?

If the Mailer does not currenly provide a [handler](notion://www.notion.so/redwoodjs/133467eb46b744fd8ae60df2d493d7d0#handlers) or [renderer](notion://www.notion.so/redwoodjs/133467eb46b744fd8ae60df2d493d7d0#renderers) for the service or technology you wish to use, this doesn't prevent you from using the Mailer. Instead, you can create your own handler or renderer which you can then open source to the wider RedwoodJS community.
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -1696,7 +1696,7 @@ Only the posts scenarios will be present in the database when running the `posts
During the run of any single test, there is only ever one scenario's worth of data present in the database: users.standard *or* users.incomplete.
### describeScenario - a performance optimisation
### describeScenario - a performance optimization
The scenario feature described above should be the base starting point for setting up test that depend on the database. The scenario sets up the database before each scenario _test_, runs the test, and then tears down (deletes) the database scenario. This ensures that each of your tests are isolated, and that they do not affect each other.
Expand Down

0 comments on commit 7ff0461

Please sign in to comment.