Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Vue 2 (deprecated) to Vue 3 #47

Open
wants to merge 23 commits into
base: dev
Choose a base branch
from

Conversation

nikeokoronkwo
Copy link

@nikeokoronkwo nikeokoronkwo commented May 17, 2024

This pull request is to address the problem of the current Flutterwave Vue library having support for Vue 2, which has reached EOL and is no longer actively maintained. There have been issues concerning this, and if there is, or will be, support for Vue 3 - #8 and #42.

In order to address these concerns, I have been able to move the api and rebuild the components and plugins in the library from Vue 2 to Vue 3. These changes include, but are not limited to:

  • Rebuilding the Vue Components used in the library to be compatible with Vue 3.
  • Rebuilding the Vue Components using the composition api rather than the options api.
  • Dropping the use of Vue.prototype in favour of composables with the useFlutterWave() composable.
  • Maintaining the same api for all components reimplemented.
  • Reimplementing the Flutterwave plugin for support
  • Removed Rollup and Babel configurations in favour of Vite.
  • Dropped the vue-cli service in favour of Vite.
  • Reimplementing and adding new tests for these components.
  • Creating a well-documented and easy-to-use API documentation for these features.

Hopefully with this, the library can begin to be used in modern Vue and Nuxt Applications to help power payments.
With this change, the flutterwave Vue plugin can therefore be used in modern-day vue and nuxt projects, with much less weight and much better performance.

@nikeokoronkwo nikeokoronkwo marked this pull request as ready for review July 5, 2024 01:31
@nikeokoronkwo
Copy link
Author

Pull request now in place

This was referenced Jul 5, 2024
@nikeokoronkwo
Copy link
Author

There has been no progress on this since July. Is there a specific reason why the team hasn't responded to this, or do they just not want to update the Vue library for users and developers to benefit from?

This is similar to what occurred in the Flutterwave Node Library, and someone had to make their own separate library (which isn't even on Github), even with the fact that the library is being actively maintained.

If the Flutterwave team no longer wants to indicate support for such libraries, they should leave it for the community to advance, rather than serving as a roadblock to needed change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants