Skip to content
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

Remove obsolete backward compatibility flag for case search dropdowns #1455

Merged
merged 5 commits into from
Sep 5, 2023

Conversation

shubham1g5
Copy link
Contributor

@shubham1g5 shubham1g5 commented Sep 1, 2023

Technical Summary

remove backward compatibility flag introduced as part of the spec as all response to FP should have it set to true now.

Safety Assurance

Safety story

Removes a obsolete flag
tested on staging.

Automated test coverage

Updated tests in the PR to test for new behaviour

QA Plan

No QA

Special deploy instructions

  • This PR can be deployed after merge with no further considerations.

Rollback instructions

  • This PR can be reverted after deploy with no further considerations.

Review

  • The set of people pinged as reviewers is appropriate for the level of risk of the change.

cross-request: dimagi/commcare-core#1325

@Jtang-1
Copy link
Contributor

Jtang-1 commented Sep 1, 2023

Can you remind me why we needed this flag in the first place? After the HQ changes were released and the remaining FP changes were done, HQ and Formplayer would have both working with keys right? What's the transitory period where FP still needed to support indexes?

Is it the transient period where a user is already in a form and then the "key" support changes of Formplayer gets deployed?

@shubham1g5
Copy link
Contributor Author

Is it the transient period where a user is already in a form and then the "key" support changes of Formplayer gets deployed?

Yes the transient period was very short only to support requests in close proximity of deploy (When user is already on case search screen before and after the FP deploy).

@shubham1g5
Copy link
Contributor Author

@Jtang-1 Flagging that this flag can be removed from Web Apps as well once this gets deployed.

@shubham1g5 shubham1g5 mentioned this pull request Sep 5, 2023
3 tasks
@codecov
Copy link

codecov bot commented Sep 5, 2023

Codecov Report

Merging #1455 (dde22ed) into master (978a051) will decrease coverage by 0.08%.
Report is 6 commits behind head on master.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #1455      +/-   ##
============================================
- Coverage     69.74%   69.66%   -0.08%     
+ Complexity     1922     1918       -4     
============================================
  Files           246      246              
  Lines          7546     7543       -3     
  Branches        676      676              
============================================
- Hits           5263     5255       -8     
- Misses         2019     2022       +3     
- Partials        264      266       +2     
Files Changed Coverage Δ
...ava/org/commcare/formplayer/objects/QueryData.java 88.23% <ø> (-0.96%) ⬇️
.../formplayer/services/MenuSessionRunnerService.java 78.41% <100.00%> (-0.61%) ⬇️

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@shubham1g5 shubham1g5 merged commit 707159d into master Sep 5, 2023
5 of 6 checks passed
@shubham1g5 shubham1g5 deleted the removeSelectValuesByKeys branch September 5, 2023 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants