-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
819 replace page text with custom page #854
819 replace page text with custom page #854
Conversation
@all-contributors |
I've put up a pull request to add @Trevor-Robinson! 🎉 |
@Trevor-Robinson Thanks for working on this! Can you take a look at the conflicts when you get a chance? |
@@ -0,0 +1,25 @@ | |||
class Organizations::Staff::CustomPagesController < Organizations::BaseController |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you are back in this for the conflicts, can you please nest these modules/class instead of inline. We are trying to move to nested slowly but surely. Not a biggie if not, but sweet if you can.
I.e.
module Organizations
module Staff
class CustomPagesController...
hey @Trevor-Robinson all you have to run now is |
Should be all good now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! @Trevor-Robinson
@Trevor-Robinson Just a heads up - I missed it in the review, but there were some issues with the naming you used on migrations. First, I am not sure why you changed the class names of the two existing migrations from PageText to CustomPage. You should never change an existing migration (the only exception might be if it's the latest one). But this can cause a lot of unintended consequences. You are better of making changes through new migrations. Also, the naming of the latest migration was wrong - i.e. the filename should always match the class name so Rails knows where to find the class when you call it. See below. These are not major issues and easy to fix, but I wanted to provide feedback. Also, I am not sure how the schema got updated with the new table name despite these migration errors...the migrations should have failed. So, did you update the file manually by chance? That's also a red flag if you had to do that. ![]() |
🔗 Issue
#819
✍️ Description
Changed all occurrences of page text to custom page. Created migration to update table name as well. All tests are passing with new name.