Skip to content
This repository has been archived by the owner on Sep 29, 2023. It is now read-only.

Ensure API endpoints have required params first #386

Merged
merged 1 commit into from
Jul 18, 2023

Conversation

stnguyen90
Copy link
Contributor

What does this PR do?

Our SDKs sort API params to make required params first (because most languages need to have required params before optional). This fixes a bug where we weren't properly sorting params in the body/payload.

Closes: appwrite/appwrite#5676

Test Plan

Manual:

image

Related PRs and Issues

Have you read the Contributing Guidelines on issues?

Yes

Copy link
Contributor

@gewenyu99 gewenyu99 left a comment

Choose a reason for hiding this comment

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

Looks good to me. @stnguyen90 How are params sorted within required/non-required groups? Does it match SDK generator, too?

@stnguyen90
Copy link
Contributor Author

Looks good to me. @stnguyen90 How are params sorted within required/non-required groups? Does it match SDK generator, too?

@gewenyu99, yes, they match.

@eldadfux
Copy link
Member

This should already come in the correct order from Appwrite, where did we see this?

@eldadfux eldadfux merged commit 60b3649 into main Jul 18, 2023
@stnguyen90
Copy link
Contributor Author

This should already come in the correct order from Appwrite, where did we see this?

@eldadfux probably 1.3 when we made the param optional.

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

Successfully merging this pull request may close these issues.

🐛 Bug Report: Wrong signature for createMembership server side implementation
3 participants