feat: refactor to expose composables

[laventnc]

What problem is this solving

As a Vuetify user I'm a huge fan of this library. However, after using libraries like vue-currency-input I think this compositional approach is better for designing libraries as you don't need to tie the implementation to a specific UI library.

Proposed solution

Break out the mask/formatting/parsing logic and expose the functionality via a composable like usePhoneInput(), similar to the aforementioned vue-currency-input library.

Describe alternatives you've considered

Perhaps this would become a different library, just wanted to throw this idea out incase you hadn't thought of it.
Huge fan of the library!

[paul-thebaud]

Hello @laventnc,

This is a good Idea for reusability inside non-vuetify projects! Many features could be extracted to pure functions or composables.

This would require a lot of work, testing, and might take longer time to maintain (more independant functions means more public API to maintain to avoid BC). I'm sorry, I do not have the time for this now.

If you want to work on a PR, I'll be happy to help and review (and extract some of the features in a secondary package for a V6). If this is something you'd like to do, please note that I would do it with more atomic features and pure functions, and multiple composables using them (not a unique big composable).

I'll keep this issue open for now as it is not fixed (even if this is not the package goal).

[laventnc]

Completely understandable. Hoping to have some free time soon, although the next year is looking pretty crazy for me.

Appreciate your insight/guidance, I completely agree. If I end up undertaking this I'll likely need some more :) !