EPMRPP-110044 || Add props to customize DateRange and DateRangeFormField components #4769
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Description
Added customization props to
DateRangeFormFieldcomponent to allow independent styling of start and end date pickers.Changes
Added four optional props to
DateRangeFormField:startPopperClassName- custom class for start date picker popperstartCalendarClassName- custom class for start date picker calendarendPopperClassName- custom class for end date picker popperendCalendarClassName- custom class for end date picker calendarUpdated
DateRangecomponent to accept and pass these props to respectiveDatePickerinstancesProps Details
All props are optional (default to empty string) and allow consumers to customize the appearance of individual date pickers independently.
PR Checklist
developfor features/bugfixes, other if mentioned in the task)npm run lint) prior to submission? Enable the git hook on commit in your IDE to run it and format the code automatically.npm run build)?devnpm script)manage:translationsscript?