You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing these Library Scope Restrictions would be much appreciated, so that we can extend custom behavior on top the existing components, without having to duplicate functionaility.
For example, if one wanted to create a month selector that would select a month in a date range of [1st of month - last day of month].
One could extend the RangeDateSelector implementation and slightly modify some of the behavior to accomplish such a case, without having to rewrite how RangeDateSelector works.
The text was updated successfully, but these errors were encountered:
Any news about this? This is needed for use cases where we want to control what the selection really should be when the user taps on a day (such as selecting a whole week, a month etc.).
Problem
Some of the
MaterialDatePicker
pre-built components have a restricted library scope;@RestrictTo(Scope.LIBRARY_GROUP)
This means that consumer apps cannot extends those classes, in order to implement more custom behavior, that is built on top of their base behavior.
Examples:
Solution
Removing these Library Scope Restrictions would be much appreciated, so that we can extend custom behavior on top the existing components, without having to duplicate functionaility.
For example, if one wanted to create a month selector that would select a month in a date range of [1st of month - last day of month].
One could extend the
RangeDateSelector
implementation and slightly modify some of the behavior to accomplish such a case, without having to rewrite howRangeDateSelector
works.The text was updated successfully, but these errors were encountered: