-
Notifications
You must be signed in to change notification settings - Fork 984
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
Group details screen (3) #14494
Merged
Merged
Group details screen (3) #14494
Changes from all commits
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
9c25609
group details screen 3
OmarBasem be63215
lint
OmarBasem 935e670
refactor
OmarBasem 631dfd7
refactor
OmarBasem 9b38612
refactor
OmarBasem 9051ae6
refactor
OmarBasem 0d35528
refactor
OmarBasem e9b8335
update status-go version
OmarBasem 4d5aaf3
refactor
OmarBasem 668529c
tests
OmarBasem 25433a8
tests
OmarBasem c39605c
refactor
OmarBasem 1bc9ff6
refactor
OmarBasem d529b89
refactor
OmarBasem 8d1524d
lint
OmarBasem 53d897c
qa fixes
OmarBasem 77a49cf
refactor
OmarBasem 1217d35
rebase
OmarBasem 1f22b54
qa fixes
OmarBasem f3dd590
lint
OmarBasem b53b304
status-go version
OmarBasem d83c87b
lint
OmarBasem 9f25807
refactor
OmarBasem 1f00fae
refactor
OmarBasem f42ddbb
rebase
OmarBasem a26da38
qa fixes
OmarBasem f0d779e
rebase
OmarBasem bda770b
rebase
OmarBasem File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Perhaps the new guidelines about Event names are not clear enough, but we almost never want to register event handlers without a qualification in the keyword.
In this case, it could be registered as
:group-chats/deselect-member
. Similarly for:group-chats/undo-deselect-member
, but never just:undo-deselect-member
.The idea being that we only want events registered without qualification if they're highly generic, reusable, but anything domain related should be qualified.
And now that I look at the event name keywords in this namespace, they are not consistent. Some don't have qualification, some use
:group
, others use:group-chats
, etc. Not saying your PR should fix this, but it'd be great to have this improved in future PRs.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.
Yes I was confused what should I name it exactly due to the inconsistency. I have opened an issue for it: #14547