Open ouattararomuald opened 3 years ago
Yeah I think everything you mentioned is valid and would make things a lot better for the codebase!
One thing ive been thinking of is a viewmodel to store the current month/year and the selection data so there's a bit more persistence on config changes, would you wanna do that in this or in another pr?
Also thank you so much for all the contributions!
I'll do it in another PR. And thank you too
Awesome!
Is your feature request related to a problem? Please describe.
CalendarPicker
is doing too much things. This makes it hard to test and it will be hard maintain in the future.Pair<String, Calendar>
. I think calendar is a very consuming object.fun addEvents(vararg events: Pair<String, Calendar>)
should propose an overload that take aCollection
Describe the solution you'd like
CalendarCellView
: to represent a day cellCalendarRowView
: to represent a row with 7 day cellsdata class Event(eventName: String, eventDescription: String, date: Date)
Collection
. It will be a good alternativeDescribe alternatives you've considered I'm open to any other alternative and discussion