-
-
Notifications
You must be signed in to change notification settings - Fork 71
Remove special case notifying author of threads #1548
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
base: develop
Are you sure you want to change the base?
Remove special case notifying author of threads #1548
Conversation
Instead of special casing creating a notification, we just have them follow normally automatically.
Remove special case notifying author of threads. This merge takes the changes so far from MoshiKoi's fork to a new branch `MoshiKoi/1025/remove-special-case-notifying-author-of-threads` in the `qpixel` repo. This will allow any qpixel developer access to continue work on this new branch and make a new pull request into `develop`.
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
…hreads' of github.com:codidact/qpixel into MoshiKoi/1025/remove-special-case-notifying-author-of-threads
Now that pull request 1548 makes post author notification of new threads part of the standard post following rather than an author-specific special case, the author needs to be a follower of the post in the test fixtures to prevent a test failing. The test is: test/controllers/comments_controller_test.rb 'Should create new thread' Line 18
…ng-author-of-threads
…ng-author-of-threads
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
…ng-author-of-threads
|
Note that there is a suggested migration approach in a comment on the original version of this pull request, which will need to be added to this new pull request before merging. I haven't implemented this migration yet because it needs to come after the migration in #1920 so I'll wait until any changes requested during its review to ensure this one is dated later than that one. |
This pull request continues from #1037 that was from MoshiKoi's fork. It's now a branch on the QPixel repo to allow any QPixel developer to work on it. See the discussion on that previous pull request.
Fixes #1025.