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

Fixes for Date Range Widget for Case Search screen #1421

Merged
merged 1 commit into from
Aug 1, 2024

Conversation

shubham1g5
Copy link
Contributor

@shubham1g5 shubham1g5 commented Jul 8, 2024

Product Description

Fixes date range widget
https://dimagi.atlassian.net/browse/QA-6604

Technical Summary

Date Range widget on mobile had a few bugs related to default value handling.It was assuming that the default values will be set in the form __range__startDate_endDate while we set those as human readable dates for ex - concat(date(today()-60) , ' to ' , date(today())) . This error doesn't surface for FP as this date conversion is done by JS code on Web Apps which is not great as well since it leads to mobile and Web Apps having separate implementation for the same functionality.

Safety Assurance

Safety story

Test for date conversion included in PR, will go through QA testing

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.

Duplicate PR

Automatically duplicate this PR as defined in contributing.md.

cross-request: dimagi/commcare-android#2779


import javax.annotation.Nullable;

public class DateRangeUtils {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shubham1g5 shubham1g5 requested review from avazirna and snopoke July 8, 2024 06:13
@avazirna avazirna marked this pull request as ready for review July 31, 2024 09:01
@avazirna
Copy link
Contributor

@shubham1g5 I believe these are also good to merge but it was as a draft, any concerns?

@shubham1g5
Copy link
Contributor Author

no concerns

@avazirna avazirna merged commit f5332f8 into commcare_2.54 Aug 1, 2024
1 check passed
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.

2 participants