Add Block users feature #879
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
driesvints
requested changes
Jul 6, 2022
Member
driesvints
left a comment
driesvints
left a comment
There was a problem hiding this comment.
Good job! Let's do these small changes already before I continue reviewing. Also maybe rebase with main. Thanks!
database/migrations/2022_06_14_072001_create_blocked_users_table.php
Outdated
Show resolved
Hide resolved
sawirricardo
added a commit
to sawirricardo/laravel.io
that referenced
this pull request
Jul 8, 2022
Co-authored-by: Dries Vints <dries@vints.io>
Co-authored-by: Dries Vints <dries@vints.io>
Co-authored-by: Dries Vints <dries@vints.io>
Member
|
Thanks for this! I took a different approach which is more in line with the current way how things work in the codebase. I also added the actual blocking of mentions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
referencing issue #698