fixture_builder
fixture_builder copied to clipboard
rdy
fixture builder based on code from fixture scenarios
Either somehow directly expose the generated name as soon as the record is created, or expose the logic to generate names. This will allow users to use the fixture name...
Here's the situation: Imagine you have a name-spaced table, e.g. `admin_users`, representing the model `Admin::User`, and this table has a JSONB column, say `details`. The `fixture_builder` gem won't ever call...
I get the following deprecation warning when using `fixture_builder` with Rails 5.0.7 several times every times the fixtures are rebuilt. ``` DEPRECATION WARNING: #tables currently returns both tables and views....
The license currently just has `Copyright (c) 2009 [name of plugin creator]` in the license file please update it with the name of the author.
`ar_internal_metadata` table was added at Rails 5.0 (ref. rails/rails#22967) for prevent destructive action on production database. It is also created on other rails environment other than production(e.g. development/test). So, I...
...to ensure fixtures are always built first, if needed. This works: ```ruby task 'db:fixtures:load' do Rake::Task['spec:fixture_builder:build'].invoke Rails.env=('development') # fixture_builder will set the env to test, we must set it back...
@rdy putting this out there to get your thoughts on it. We've been using this and it's been really handy for a couple custom things. Lmk what you think and...
