[REFACTOR]: [Opayo] Remove Default Case Handling

[Sakilmostak]

📝 Feature Description

• We utilize match statements to make pivotal decisions, such as generating requests based on the payment method type and managing responses received from the connector.
• These conditions generally go hand in hand with enum variants.
• Default case is used because a match statement needs to be exhaustive i.e. every variant needs to be covered.
• So, if all the explicit cases are handled then default is used to handle the rest.
• Each connector have these match statements but many of them don’t provide reference to each variant in their default case, rather a _ is put to handle all the other cases.
• This approach carries a risk because developers may inadvertently overlook the need for explicit handling of the new cases.

🔨 Possible Implementation

• Instead of relying on a default match case _, developers should handle each and every variant explicitly.
• By doing so, if there are any changes in the future, they can readily assess the impact of their modifications simply by compiling the code.
• You can check this PR for further reference refactor(connector): [Zen] refactor Zen payment methods not implemented errors #1955

🔖 Note: All the changes needed should be contained within hyperswitch/crates/router/src/connector/

📦 Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

📦 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

✨ Are you willing to submit a PR?

[Abhiramjampani]

@AkshayaFoiger @Sakilmostak @VedantKhairnar
I would be delighted to work on this issue
so kindly assign me this issue
Thank You : )

[AkshayaFoiger]

Hey @Abhiramjampani , I see that you're already assigned to #2346. For now, we'll leave this issue open to any other interested contributors. You may pick this up once your work on #2346 is completed, and if no other contributors have expressed interest on this. I hope that's fine by you

[amaan14999]

Hi @AkshayaFoiger. I would be delighted to work on this issue. My previous PR is under review and in merging process.

[Sakilmostak]

Hello @amaan14999 , thanks for the submission. I have assigned this issue to you👍

[amaan14999]

Hey @Sakilmostak, thanks for the update but the issue has not yet been assigned to me.

[amaan14999]

@Sakilmostak @VedantKhairnar @AkshayaFoiger can this issue be please assigned to me?

[SanchithHegde]

@amaan14999 Done, sorry about the confusion.

[swangi-kumari]

Hello @amaan14999 ,
Are you still working on this issue?
Please let us know if you need any help:)

[Hangsaai]

Hey @swangi-kumari can you assign this to me as I have already raised a PR and want to work on this

[amaan14999]

Hey @swangi-kumari, I tried but was not able to resolve the issue since I am new to Rust. Kindly unassign me.

[swangi-kumari]

Hey @swangi-kumari, I tried but was not able to resolve the issue since I am new to Rust. Kindly unassign me.

Sure, Glad that you tried:)

[HeetVekariya]

@swangi-kumari can you please assign me this issue, as i have worked on the similar issues.

[deepanshu-iiitu]

Hey @Hangsaai , sure! I've assigned this to you.

In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with

[deepanshu-iiitu]

@swangi-kumari can you please assign me this issue, as i have worked on the similar issues.

Hey @HeetVekariya ,
Actually we assign the issue on FCF basis. If you are interested you can pick some other open issues.

[HeetVekariya]

@swangi-kumari can you please assign me this issue, as i have worked on the similar issues.

Hey @HeetVekariya ,
Actually we assign the issue on FCF basis. If you are interested you can pick some other open issues.

No worries, I haven't seen that comment