Open mzagaja opened 5 years ago
@mzagaja there are two possible solutions to this issue:
1- edit the original migration that the extension generated; both in in vendor/extensions/db/migrate/
and db/migrate/
and change the column
2- generate a migration in the actual application using normal Rails techniques (so you don't need a spec/dummy inside the extension's folder) and then copy it to the vendor/extensions/db/migrate/
folder. You may wish to rename it with the prefix to 2-
instead of the date stamp so that rails g refinery:stories
still works as expected if you ever regenerate or share your extension.
The error message you're seeing is expected as the "app" in vendor/extensions/stories has no Rails app with which to generate migrations. I'm not sure why you're seeing it after you already generated an extension.
Hope that helps to provide context around how the design of this works and to provide a workaround.
I'm going to leave it open as the continued errors you described (listen & the follow up refusal to generate a migration) are unexpected.
After creating an extension called "Stories" I would like to rename the field "email" to "name" because I would prefer the user just provide their name instead of email.
Then I run it again and receive the same error:
As a side note I will add I had to add the listen gem to my extension Gemfile to successfully generate the dummy app.
Refinery CMS section of Gemfile is as follows: