Skip to content

Conversation

@Abraham-Flutterwave
Copy link
Contributor

Highlights:

  • Dynamic User-Agent Header: More control over HTTP requests for better environment integration.

  • Enhanced Transaction Tracking: Deeper insights into transaction events for better fraud detection & debugging.

  • Expanded Test Coverage: More robust testing for increased reliability and stability.

  • Refactored Card Service: Improved performance and maintainability for card-related transactions.

  • Default Modal Customization: Set the default checkout flow modal for a more tailored user experience.

And More! Bug fixes, performance optimizations, and development workflow improvements.

Benefits:

  • Simplified development, improved performance, enhanced security, and greater flexibility.

This commit updates the HTTP client code to set the 'User-Agent' header dynamically based on the SDK version. The User-Agent now follows the format 'FlutterwavePHP/{SDK_VERSION}', where {SDK_VERSION} is the version of the SDK obtained from the EnvVariables class.This change improves the clarity of user-agent information for HTTP requests, helping with tracking and debugging.
The Transaction Service no longer requires a separate event handler as it not has the trait of a event handler.
handle request via the command line using set environment variables.
Update Test using new Test cards.
handle custom configurations using PackageConfig::setUp()
the payment controller makes use of the flutterwave standard method by default
This fix ensures that an existing configuration is not overriden
array merge compatibility with 7.4
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

@corneliusyaovi corneliusyaovi merged commit d495379 into Flutterwave:dev Apr 9, 2025
1 check passed
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.

3 participants