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

[ACS-6107] Updated default configuration for date-range component to be compatible with the new advanced search date range component #3532

Merged
merged 3 commits into from
Dec 26, 2023

Conversation

swapnil-verma-gl
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:
    Updated default configuration for date-range component to be compatible with the new advanced search date range component

What is the current behaviour? (You can also link to an open issue here)
The default configuration for date range component was according to the older date-range component

What is the new behaviour?
Updated the configuration to be compatible with the new advanced search date range component

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

@swapnil-verma-gl
Copy link
Contributor Author

Added the 'do not merge' label as this PR is not to be merged with develop until the corresponding ADF PR is merged and upstreamed into ACA. This is to ensure that there is no incompatibility issues in case this PR gets merged before an upstream

@@ -1028,14 +1028,16 @@
{
"id": "createdDateRange",
"name": "SEARCH.SEARCH_HEADER.FILTERS.DATE.TITLE",
"columnKey": "createdAt",
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No this was not intentional. I've restored it

@swapnil-verma-gl swapnil-verma-gl force-pushed the dev-swapnil-acs-6107-remove-old-date-range branch from 288c426 to 28a0a22 Compare December 5, 2023 07:39
Copy link

sonarqubecloud bot commented Dec 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@swapnil-verma-gl swapnil-verma-gl merged commit 339dc60 into develop Dec 26, 2023
25 checks passed
@swapnil-verma-gl swapnil-verma-gl deleted the dev-swapnil-acs-6107-remove-old-date-range branch December 26, 2023 05:44
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