🐛 Bug Report: Updating attributes doesn't allow null defaults, min, max etc

[pingu2k4]

👟 Reproduction steps

Databases.UpdateStringAttribute and others such as email, ip, url etc - the xdefault parameter could be null but the parameter it expects is non nullable. Also, for things like updating an "integer" attribute, the min, max and default are all non nullable, and its not possible to pass null into these at all.

👍 Expected behavior

Should accept nullable values for default

👎 Actual Behavior

Deson't accept nullable values

🎲 Appwrite version

Version 0.10.x

💻 Operating system

Windows

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

[adityaoberai]

Hi @pingu2k4 Just want to double check that the Appwrite version is correct? Because the current version of the SDK is not meant for v0.10

[pingu2k4]

Hey, this was on V 1.5.x of Appwrite. Not sure what you mean with V 0.10 sorry?

[adityaoberai]

Hey, this was on V 1.5.x of Appwrite. Not sure what you mean with V 0.10 sorry?

Sorry, I noticed this here and it had me confused 😅

[pingu2k4]

Ohh, thats my bad... I have no idea why I put that... Complete accident sorry!

[adityaoberai]

Haha, no worries

I just noticed the error you have mentioned. Sorry about that.

I'll definitely discuss this with the team ASAP. Just as a general note, the best place to raise SDK-related issues is the SDK-generator repo.