-
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 + bonus Aug 20] Block ability to select Chronos from Recents list when splitting bill or requesting money #4411
Comments
Triggered auto assignment to @mateocole ( |
If this is a valid issue then, Proposed Solution
or
Accordingly update and add the following check
|
Hey, I too found the same issue just about half an hour ago. Wondering coincidence or hack? 🤔 |
But for the concierge. |
Okay, yours is a different issue, you are choosing |
Triggered auto assignment to @aldo-expensify ( |
Triggered auto assignment to @stephanieelliott ( |
Can you block from recent You had already noticed this. |
@mateocole, @stephanieelliott Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Ok I took a look at #4413 and I'm not sure I understand the difference between these two issues. It sounds like @mananjadhav and @Santhosh-Sellavel understand these as two separate PRs, can you please share a little more detail on the difference here? Once I am sure these are duplicates, I can move this to Upwork and get the proposal reviewed 😃. |
#4413, deals with the data from the API and the search. This one deals with the recent chats. |
Simple @stephanieelliott, Before creating any IOU Requests, just message But in #4413, Hope you got cleared! |
@stephanieelliott Both look similar, it's really not. It's a coincidence we found these similar issues almost at the same time. IMO It's not a duplicate. |
Ah got it, thanks so much for the clarity @mananjadhav and @Santhosh-Sellavel! Here is the job on Upwork: https://www.upwork.com/jobs/~01254c03b03bc32ed4 |
@Jag96 @stephanieelliott I've sent the proposal on Upwork. @Jag96 Then are we saying we'll add that many parameters to the function call? I would recommend option 2, because you'll have one parameter, and if the list grows we won't have to add params, only adjust the flags in one object param. Will let you decide and then implement.
Also, apart from chronos, concierge and receipts which are the other automated accounts? |
I think option 2 is fine as long as we make sure JSDocs are added appropriately, so for example anywhere we'd have a check for Right now I think the only three we want to check are concierge, chronos, and receipts, so that sounds ok to me. Let me know if that makes sense! |
Got it. Noted. Will handle it accordingly. |
@stephanieelliott #4413 sounds the same and look like two contributors are working on the same thing. Maybe changing the title to show the difference is a good thing to do. |
I had already changed the titled to differentiate between the two... #4411 deals with choosing |
I'm taking an extended OOO, re-applied the External label to get another CM to take this the rest of the way, thanks @Christinadobrzyn! |
The PR for this issue is here. |
Looks like Upwork job autoclosed - so reopened: Internal posting here - https://www.upwork.com/ab/applicants/1428898063992438784/job-details Hired @mananjadhav - sorry Manan but can you let me know when you accept the hire request so I can pay you? |
@Christinadobrzyn I just texted you on Upwork. While I did accept the current offer, I can see the old job as well in the contract. Will you take care of closing the one of them? |
Ah thank you @mananjadhav I was able to pay you through the original job posting. Closed the second job I created. |
Thanks @Christinadobrzyn |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
I am not quite sure of the role of Chronos. Can be closed if this is an incorrect assumption.
Action Performed:
Expected Result:
It shouldn't allow split/request money transactions with Chronos.
Actual Result:
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: