We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go to https://appwrite.io/docs/server/teams?sdk=nodejs-default#teamsCreateMembership and look at the example, the order of parameters are:
But when using the SDK on my project, the order is actually
I was expecting the documentation and the SDK to be consistent.
Actually - I would prefer if the functions just accept an object with the parameters as properties:
await teams.createMembership({ teamId: TEAM_ID, userId: USER_ID, email: EMAIL, url: URL, roles: [] });
This way, the order in which you provide the parameters do not matter at all.
The SDK and the docs aren't consistent.
Version 1.3.x
Linux
"node-appwrite": "^9.0.0",
The text was updated successfully, but these errors were encountered:
Can I work on this issue?
Sorry, something went wrong.
This has been fixed, not released yet: appwrite/docs#381
Okay, thank you @joeyouss
Closing this issue in favor of PR appwrite/docs#381
joeyouss
No branches or pull requests
👟 Reproduction steps
Go to https://appwrite.io/docs/server/teams?sdk=nodejs-default#teamsCreateMembership and look at the example, the order of parameters are:
But when using the SDK on my project, the order is actually
👍 Expected behavior
I was expecting the documentation and the SDK to be consistent.
Actually - I would prefer if the functions just accept an object with the parameters as properties:
This way, the order in which you provide the parameters do not matter at all.
👎 Actual Behavior
The SDK and the docs aren't consistent.
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
"node-appwrite": "^9.0.0",
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: