-
Notifications
You must be signed in to change notification settings - Fork 1
Conversation
Thanks for contributing to Dialtone Vue! Please read below for some important info regarding Vue 3 compatibility. Currently we need to maintain two branches in Dialtone Vue, one for Vue 2, one for Vue 3. This means you must create two PRs for every feature change you make. One into Many times the change you have made in Vue 2 will be identical to the change you need to make in Vue 3. To make this easier we have made a script that can copy your changes from this branch to a new branch off of staging-vue3 suffixed with -vue3. run Once the new branch is created, you will need to look at your code to make sure it still makes sense and test that your changes all work in vue 3. If everything is good you can push it and create a PR into It is a required check for every PR to have a corresponding branch called I got "commit SHA is a merge but no -m option was given."This happens if there are merge commits in your branch. It's no problem, you can simply skip them with What if I make more changes to my vue 2 branch after running ./copy_pr_vue3.sh?You can copy these to the existing -vue3 branch by running the script with a git SHA param like so:
where 2a78db7 is the last commit from your branch that was copied to the other branch (all commits after this will be copied) If it's just one or two commits, you may prefer to just manually use What if I get a conflict?It's possible to get a conflict when running |
βοΈ Deploy Preview ready! |
a11y test fail on
|
Cool, looks good, I would revert the update in This is my suggested change to Also it would probably necessary to remove
This is the final result: Ping @tonydialpad here to check out this suggested change. |
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.
Pre-approving it but need to fix the a11y issue.
Looks good improvement for avatar component, feel free to update recipes/list_items/contact_info/contact_info.vue
component here, or create a ticket to update it later.
It will be necessary to update also the vue3 version of it, but is still pending 1177
components/avatar/avatar.vue
Outdated
}, | ||
]" | ||
:tabindex="clickable ? 0 : -1" | ||
:role="clickable ? 'button' : 'presentation'" |
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.
Can we change the actual element instead of just setting role? Can we have some sort of indicator on hover to show it is clickable? Maybe overlay it with a dark color with some opacity?
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 element should I use instead, a button?
Maybe I can show the focus ring on hover too, I was using cursor: pointer
to show it is clickable on hover but maybe the opacity would work better.
@francisrupert @fede-dp please help us on this decision.
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.
Yeah it should be button I think
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.
updated
components/avatar/avatar.vue
Outdated
keydown: (e) => { | ||
if (!['Space', 'Enter'].includes(e.code)) return; | ||
e.preventDefault(); | ||
this.$emit('click', e); | ||
}, |
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.
I think we wouldn't have to worry about all this if the element was an actual button
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.
I'll try with a button
βοΈ Deploy Preview ready! |
Sorry this got buried in my notifications. Yes, button.
I don't mind the |
βοΈ Deploy Preview ready! |
Fixed, good catch! |
Created a ticket to solve this later: https://dialpad.atlassian.net/browse/DLT-1230 |
βοΈ Deploy Preview ready! |
Updated please re-review. |
βοΈ Deploy Preview ready! |
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.
Yeah, it might, I have two options here: Making the border inset or adding the border to the non-clickable version which might cause a misalignment too. Any advice here? @francisrupert |
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.
Great, thanks!!
βοΈ Deploy Preview ready! |
Added the border by default to the clickable avatar and just change the color on :hover and :active, this will increase the size of avatars which I don't think it's to much of an issue because this way the size will not change. I was thinking on adding it to all the avatar, but that'd increase the size of all the avatars across the app and that'd create a lot of issues with QA |
βοΈ Deploy Preview ready! |
# [2.97.0](v2.96.0...v2.97.0) (2023-09-20) ### Bug Fixes * add virtual "prompt" for visual tests on PR ([#1192](#1192)) ([4a41d02](4a41d02)) * **Avatar:** change avatar seed algorithm to sync with android ([#1182](#1182)) ([53a09f3](53a09f3)) * **Contact Info, Feed Item Row, Item Layout:** alignment issues ([#1186](#1186)) ([bdaa355](bdaa355)) * feed pill not exported ([#1180](#1180)) ([792b838](792b838)) * **Item Layout:** selected slot alignment ([#1194](#1194)) ([09c37c4](09c37c4)) * **Recipe Callbar Button With Popover:** change event name and sync open state ([#1183](#1183)) ([b91dc02](b91dc02)) ### Features * **Avatar:** add clickable behavior ([#1176](#1176)) ([2b80018](2b80018)) * **Callbox:** add clickable behavior ([#1196](#1196)) ([bf5ac2b](bf5ac2b))
π This PR is included in version 2.97.0 π The release is available on GitHub release Your semantic-release bot π¦π |
Feat (Avatar): Add clickable behavior
π οΈ Type Of Change
π Description
clickable
property todt-avatar
to enable the possibility to focus and click on avatars.π‘ Context
Callbox component needs to emit an event when clicking on the avatar, also in this PR a clickable avatar was needed and a custom implementation was made, so I thought that maybe a clickable avatar is a good feature to have.
π Checklist
π· Screenshots / GIFs