Datepicker swappable engines idea about ng-bootstrap HOT 3 CLOSED

Do we need to import the original? Is it not possible to provide an abstract class or interface?

from ng-bootstrap.

Or maybe one idea is to provide a dummy class with methods as DatepickerEngine and force users to extend it and provide that.

from ng-bootstrap.

Downside is that if the user don't use it, app won't work, but I think that is a convention in angular 2.

I think that we can easily avoid this issue by sth like:

class NgbDatePicker {
    constructor(@Optional() private _settings: DatepickerEngine = new DefaultDatepickerEngine()) {
    }
}

This way people will get defaults if they don't provide anything.

Also, I think that if there are 2 providers under the same token they will override each other (the last one wins). So we could export NGB_PROVIDERS or NGB_DATEPICKER_PROVIDERS with defaults.

I think we can close this now as the general idea here is good and we can figure out technical details (if there is anything left to figure out) when actually working on the implementation.

from ng-bootstrap.