Refactor RazorpayClient to Actor Model and Update Documentation Configuration #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…xclusion - Changed `RazorpayClient` from a class to an actor for improved concurrency handling. - Removed exclusion of `Documentation.docc` from the package configuration.
vamsii777
added
semver/major
vamsii777
added
semver/major
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request refactors the
RazorpayClientfrom a class to an actor to improve concurrency handling. Additionally, it removes the exclusion ofDocumentation.doccfrom the package configuration, allowing for better documentation management.Type of Change
Motivation and Context
This change is required to leverage the actor model for better concurrency management in the
RazorpayClient. The previous implementation as a class could lead to potential issues with concurrent access.How Has This Been Tested?
The changes have been tested by running existing unit tests to ensure that the functionality remains intact after the refactor. The testing environment includes Swift 5.8 and the latest version of the AsyncHTTPClient. All tests related to the
RazorpayClientwere executed successfully.Checklist
Breaking Changes
The change from a class to an actor may affect existing implementations that rely on the
RazorpayClientbeing a class. Users may need to adjust their code to accommodate the actor model's concurrency features.Additional Notes
No additional notes at this time.