Thanks for opening a PR! I like the idea, but I guess it's better to do this with fecha, which is included as a dependency to perform date operations in this library. I will investigate this feature and use your PR for this. Contributions are welcome 👐

I'll see if I can integrate fetcha into the string localization when i'm at work today and push another commit to the PR. Usually its slow as heck

Just want to make sure i'm not missing anything.

this.props.dateService.format(date, dateFormat)

Which gets defined in

 static defaultProps: Partial<BaseDatepickerProps> = {
    dateService: new NativeDateService(),

And the date service gets imported from
import { NativeDateService } from '../calendar/service/nativeDate.service';

And the format function being called in nativeDate.service.ts in my change is

  public format(date: Date, format: string): string {
    return fecha.format(date, format);
  }

So no changes should be necessary? The only difference is allowing users to specify the string instead of hardcoding it as a const. Fecha was already doing the string localization to begin with, just with a hardcoded date format

@nutritiousreject yes. You may need to call format here. Same for Range Datepicker