Removing Hooks for plugins

[Eonasdan]

I created the two hook options for turning the date objects to string and conversely take a value and returning a DateTime object. This was to allow devs to use an outside library like moment/luxon/dayjs to handle those things if the Intl formatting wasn't good enough.

I've now added a plugin system and I think I'd rather use that system instead of the hooks. Plugins are more self contained and can be reused and shared.

Questions? Comments? 👍or 👎

[William-H-M]

I personally prefer to be the library to be the one doing the formatting with whatever library/plugin is used, so that way I can check what library to use as time manager.

For example, with the older release was something like, ok, so moment is needed? Then moment all the way for managing times (still do, even if deprecated 🤷‍♂️ )

Given the case would prefer the plugin system, but that the library comes with one by default and of course if you don't like that one on specific there may be a plugin available, or you can implement your own!

[Eonasdan]

Yes it's the same with the hooks. If no options are provided then I'll use the internal date object. I'm using the native JS Date + some convenient extensions and using Intl to format the dates to the textbox. Intl is no where near as powerful as something like moment so the hooks are a way to allow people to deal with it externally if they want. I'm consider migrating those hooks back out of the options and just let a plugin overwrite the default methods.

[Eonasdan]

This is done. Its currently in the dev branch. I've made a momentjs plugin as an example