[REFACTOR]: [Worldline] 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?

[nik132-eng]

can you assign me this issue?

[AkshayaFoiger]

Hey @nik132-eng , 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

[VedantKhairnar]

Hey @nik132-eng ,
Let us know if you face any issues. Happy to help! : )

[VedantKhairnar]

Hey @nik132-eng ,
Just checking in - are you working on it or shall we consider reassigning it to someone else?

[swangi-kumari]

Hello @nik132-eng , we didn't hear back from you, so we are unassigning you from this issue. If you are interested, we will assign you with other issues, if the current one is taken.

[Hangsaai]

Hey @swangi-kumari can you assign this to me I am willing to submit PR

[swangi-kumari]

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.

[Hangsaai]

Thank you @swangi-kumari for assigning me this issue. I have started working on this.

[Hangsaai]

I am not able to push the code shows that I am not a collaborator @swangi-kumari

[Hangsaai]

[swangi-kumari]

Hey @Hangsaai ,
Disable browser extensions and try, or you can also try it with a different browser without any extensions installed.

[Hangsaai]

Yep I have already tried using Brave aswell but same problem occuring

[SanchithHegde]

@Hangsaai Which repository are you trying to open a pull request from? Please ensure that you have write access to the repository you're opening the PR from.

[Hangsaai]

I am directly pushing to a branch in hyperswitch itself and then creating a PR to main @SanchithHegde

[SanchithHegde]

@Hangsaai Could you please share the link to the repository/branch you're pushing to?

[Hangsaai]

Here @SanchithHegde https://github.com/juspay/hyperswitch/tree/wordline

[SanchithHegde]

@Hangsaai Ideally you shouldn't have had access to push a branch to our repository. Could you push the branch to your fork instead and open a PR from there?

[Hangsaai]

Yep I just figured it out I guess it's a vulnerability of github shouldn't have happened

[Hangsaai]

Hey @SanchithHegde @swangi-kumari , can you guys assign this issue to me.

[swangi-kumari]

Completed in 2674