Daniel Colson

Yup, that seems to match the solution in #1096. I think you could use `after(:build)` instead of an `after(:create)`, then get rid of the call to `save!`.

I haven't spent too much time thinking about an official solution for this. I could imagine something like: ```rb factory :person do skip_aliases # ... end ``` to opt-out of...

We have a [Code of conduct](https://thoughtbot.com/open-source-code-of-conduct) that we expect all contributors to follow.

Sure, I'm all for adding a relevant example to the documentation, maybe somewhere around https://github.com/thoughtbot/factory_bot/blob/master/GETTING_STARTED.md#specifying-the-class-explicitly

Nice idea. What if we forward the block along: ```diff elsif __valid_association_options?(association_options) - association(name, association_options) + association(name, association_options, &block) ``` So we can get the error already defined in the...

Yeah, that would be great. Thanks!

If you're using Rails, you could probably get some of this by using [`with_options`](https://api.rubyonrails.org/classes/Object.html#method-i-with_options). For example: Code example ```rb # frozen_string_literal: true require "bundler/inline" gemfile(true) do source "https://rubygems.org" git_source(:github) {...

https://stackoverflow.com/questions/55141549/attatching-activestorage-files-in-factorybot https://blog.eq8.eu/til/factory-bot-trait-for-active-storange-has_attached.html

I had the same thought about this maybe being in factory_bot_rails in https://github.com/thoughtbot/factory_bot/pull/1317#issuecomment-513345549, although I agree with you that might be less discoverable.

Draft PRs https://github.com/thoughtbot/factory_bot/pull/1317 https://github.com/thoughtbot/factory_bot/pull/1327