-
Notifications
You must be signed in to change notification settings - Fork 435
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
feat: show conversation settings, if URL hash is specified #13503
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Maksim Sukharev <[email protected]>
} else if (this.$route.hash === '#settings') { | ||
emit('show-conversation-settings', { token: this.token }) |
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.
This feature is a conversation-only feature, but handled here on a whole app level:
- It handles hash and emits conversation-related event on all the pages without conversation (token)
- Though it works right now, there is no guarantee conversation components are mounted and ready at this moment. It will be broken if we add anything async to the conversation page init.
- It uses
settings
fragment, leaving no tinny name for Talk settings if we add it 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.
What about moving it to the conversation view?
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.
And about removing the hash from URL when the settings dialog is open
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.
- ConversationSettingsDialog is detached and independent from conversations. So it could be called on empty view as well, contrary to
#direct-call
- It requires only token+conversation object to work. Maybe some additional request is needed here to ensure we fetched a conversation prior to opening the dialog
- Removing of hash should be fine, as long as it doesn't triggering any vue-router side effects
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.
- as long as it doesn't triggering any vue-router side effects
If it does, it is a bug that should be fixed
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.
It requires only token+conversation object to work
We don't have token+conversation outside the conversation view.
And a fragment cannot specify it. If we want to add ability to open setting for any conversation, it must be a query param. (Or if we want it to be combined with other fragments, like message id).
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.
☑️ Resolves
#settings
link to directly open conversation settings #13485#direct-call
🖌️ UI Checklist
🖼️ Screenshots / Screencasts
🏁 Checklist