-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2022-01-27] Feature Request: Change emoji navigation with arrow keys #7035
Comments
Triggered auto assignment to @bondydaa ( |
Triggered auto assignment to @johncschuster ( |
Proposal: App/src/pages/home/report/EmojiPickerMenu/index.js Lines 180 to 183 in fbb4674
Change the if condition to:
I am working on this #6977 and have moved the location/renamed files, etc. for the EmojiPicker. I can take this up as a follow-up PR and add the feature. cc - @mallenexpensify |
LGTM! |
sending to the pool |
@bondydaa @johncschuster Nobody’s assigned to the issue after being unassigned |
@bondydaa as the engineer assigned can you add the internal or external label? |
is sending to the engineering pool no longer an option? I guess external is probably fine but for new feature requests I think letting this go to the pool and have someone who's more involved in new dot review is better than me just willy nilly saying sure go for without any context. |
posted about this in engineering-chat to see if someone more familiar with new dot wants to review first |
Triggered auto assignment to @JmillsExpensify ( |
Hmm, yeah I agree with @mvtglobally. Posting to Upwork shortly. In fact, I think what we have currently is more like a bug. |
Upwork job is here: https://www.upwork.com/jobs/~016537449e7470b466 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @luacmartins ( |
@mananjadhav your proposal looks good! |
📣 @mananjadhav You have been assigned to this job by @luacmartins! |
Yup, @mananjadhav's proposal looks good. |
I am working on #6977 PR, can I combine this one in that PR? |
Sure, that's fine. Just make sure to link this issue there as well. |
I'm really sorry, I missed this. @mananjadhav |
No problem. I’ll finish that one by tomorrow and probably keep this on hold? |
Sounds good. Plus it's a feature request |
@mananjadhav any updates on when your PR will be ready for review? Thanks :) |
Put in an update on the PR. |
@rushatgabhane @luacmartins PR updated |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.31-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-01-27. 🎊 |
No regressions. @mananjadhav Payment processed. @mvtglobally Thanks for reporting. I closed the above Upwork contract so I created a new job for you to apply for here: https://www.upwork.com/jobs/~01e92d1d2a7f6a2c45. Thank you all! |
@JmillsExpensify sorry to ping you, I've applied to the same job. I hope that's okay! |
Ah thank you! Will handle, apologies for missing. |
All contributors should be successfully paid at this point. Closing the issue, but please reach out if I can help with anything or if I missed something! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
User should navigate to the first emoji listed below (the same as if you clicked the down arrow)
Actual Result:
Nothing happens when you click right arrow
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.25-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Recording.371.mp4
Expensify/Expensify Issue URL:
Issue reported by: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1640907606322500
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: