Make century detection configurable

[stefan-niedermann]

Is your feature request related to a problem? Please describe.

The datepicker allows to enter a date like 02.02.02 and automatically adds the century: 02.02.2002. Unfortunately the detection of the century is currently hardcoded and switches at the year 68:

https://github.com/valor-software/ngx-bootstrap/blob/9c906398facdb5c1177e150ba3dc9414c9090086/src/chronos/units/year.ts#L71-L73

This is insufficient for our use case as we have our own company defaults

Describe the solution you'd like

Make the switching year (currently 68) configurable.

Describe alternatives you've considered

• Allow to pass an own century detection strategy
• Currently we are monkey patching ngx-bootstrap in the node_modules folder with a postinstall npm script. This is not a solution but a dirty, hacky and unreliable workaround.

Additional context

This has been requested multiple times without an satisfying answer, for example:

• 5322 where it seemed that you did not understand the issue as you closed it with an unrelated answer.

• 4476 where you closed it with a hint to moment.js which is not true. According to the moment.js docs it is configurable in moment.js

  This can be changed by replacing the moment.parseTwoDigitYear method.

[vintageluke]

+1