-
Notifications
You must be signed in to change notification settings - Fork 114
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
Rename DefaultPetTask to Checklist::TaskTemplate #834
Comments
@kasugaijin can I take this one? |
@ErinClaudio all yours |
@ben @mononoken I have a couple of things that are going to keep me busy and unable to work on this until Wednesday. I am happy to start this then but I do not want to block anyone else's work. please feel free to give this away if needed |
OK, I will unassign now and if it's free on Wed pick it up! @ErinClaudio |
Ok - I can do this one now @kasugaijin |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Automatically unassigned after 7 days of inactivity. |
DefaultPetTask should be renamed to Checklist::TaskTemplate. This means renaming all areas in the app (table (default_pet_tasks), model, controller, policies, views, tests, variables, methods etc.). It should be a relatively straightforward find and replace.
Note the table should be renamed to task_templates_table. The Checklist scope helps to organize this resource along with others that are similar.
please nest the classes instead of inline: https://thoughtbot.com/blog/why-you-should-nest-modules-in-ruby we are trying to move to the nested format throughout.
Any questions - comment below!
The text was updated successfully, but these errors were encountered: