Mechanism for Using Emepheral Database Records in Previews

[dyeje]

Feature request

Some mechanism similar to RSpec use_transactional_fixtures for component previews.

Motivation

We often pass active record objects into our components. Currently, we fetch records and hope they have the properties we need. What would be great is if we could use factory_bot or similar to create the exact records we need for a preview. We could do that currently, but it would pollute our local database each time we view the preview. It'd be nice if we could generate the markup and then throw away the records similar to how a component spec works.

[Spone]

Hi @dyeje! Have you tried wrapping the render method from the preview in a transaction? If you provide an example that solves your issue, we could look at how to implement it in ViewComponent.

[dyeje]

Good idea, we'll give it a shot.

[BlakeWilliams]

Currently, we fetch records and hope they have the properties we need. What would be great is if we could use factory_bot or similar to create the exact records we need for a preview. We could do that currently, but it would pollute our local database each time we view the preview.

I've implemented similar in the past, but instead of using real records I used FactoryBot's build and build_stubbed functionality to avoid having to deal with creating real records in the environments you're running previews in.