fw-datepicker about crayons HOT 4 CLOSED

• Can we have 'mode' as and attribute that can have 'range' and other attributes instead of specifying singledatepicker?

okay I'll rename and change the boolean type to string with ('range'/'single date')

• missing things like value. To fetch the date.

I thought of reuse startDate as value for singleDate(not good idea though). I'll add value which is for mode 'single date'

• If you are doing time selection, do we need to add more attributes?

startTime and endTime attributes only will be extra to it for time selection.

• Should component be compatible with i18n?

I do have that doubt, if it's okay to add in next update, we can hold.

• fwChange

will rename the event name

from crayons.

@sathishkumar-thangavel A few doubts questions:

• Can we have 'mode' as and attribute that can have 'range' and other attributes instead of specifying singledatepicker?
• missing things like value. To fetch the date.
• If you are doing time selection, do we need to add more attributes?
• Should component be compatible with i18n?
• fwChange

from crayons.

@asifahmedfw as I'm discussed with designer, timepicker can be a seprate component, people mostly not using and it'll be complex. So updated the properties above( removed timepicker properties)

from crayons.

@sathishkumar-thangavel There is already a timepicker. Datepicker needs to have a timepicker. You can take that in second phase but make sure no interface changes when you introduce timepicker.

from crayons.