-
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
[$250] [HOLD for Payment 2024-09-06][Search v2.1] Include policyID in the Search AST #46592
Comments
Triggered auto assignment to @mallenexpensify ( |
@luacmartins Is this waiting on backend changes? |
Same question as @rayane-djouah , I'm unsure of next steps (and commenting to remove |
I think @Kicu might work on this one. Can you confirm? |
yes! I'm working, thanks for pointing out this issue, I missed it |
@luacmartins draft is ready so you might want to take a look. This is surprisingly complex, because I had to make sure all the different cases where we might set Tomorrow I will polish this up and finish the checklist |
Nice! Thanks for linking the draft. I'll take a look at it today. |
one thing I forgot to mention - I believe now that |
I saw that last night when working on another PR. Yea, I'll work on this today. |
Note The production deploy automation failed: This should be on [HOLD for Payment 2024-09-6] according to #48221 prod deploy checklist, confirmed in #47787 (comment). |
Not overdue. Payment is due on the 6th |
Job added to Upwork: https://www.upwork.com/jobs/~021833303422059505984 |
Current assignee @rayane-djouah is eligible for the External assigner, not assigning anyone new. |
@rayane-djouah can you please accept the job and reply here once you have? I'm assuming this issue is $250. |
@mallenexpensify I applied to the job |
@rayane-djouah , I think I accidentally sent you an invite without hiring you, which I did just now. Can you please accept the job and reply here once you have? |
@mallenexpensify Accepted, thanks! |
Contributor+: @rayane-djouah paid $250 via Upwork I'm assuming we don't need a regression test here and that they'll be created as part of the Search project. Thx! |
Problem
Currently, we send the policyIDs as a Search API param, however it should be parsed an included in the AST, like we do for other filters.
Solution
Include
policyID
in the parser grammar and stop sending thepolicyIDs
paramIssue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: