🐛 Bug Report: undocumented change of order of parameters in `updateIntegerAttribute` and `updateFloatAttribute`

[hej2010]

👟 Reproduction steps

In the latest release (16.0.0) the updateIntegerAttribute and updateFloatAttribute input parameters changed from:
databaseId, collectionId, key, required, min, max, xdefault?, newKey?

sdk-for-node/src/services/databases.ts

Line 1042 in f75abab

updateIntegerAttribute(databaseId: string, collectionId: string, key: string, required: boolean, min: number, max: number, xdefault?: number, newKey?: string): Promise<Models.AttributeInteger> {

to
databaseId, collectionId, key, required, xdefault?, min?, max?, newKey?

sdk-for-node/src/services/databases.ts

Line 1031 in 91783da

updateIntegerAttribute(databaseId: string, collectionId: string, key: string, required: boolean, xdefault?: number, min?: number, max?: number, newKey?: string): Promise<Models.AttributeInteger> {

but the release notes does not mention this.
I got a lot of errors in my app (Invalid 'max' param: Value must be a valid integer) until I checked the code changes :)

👍 Expected behavior

Release notes should mention this

👎 Actual Behavior

Release notes did not mention this

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

No response

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

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[ChiragAgg5k]

@hej2010 hi there, sorry for the trouble that this changed might have caused. it was made because min and max params are now optional and hence needed to be pushed back after the required params.

the version of the library had a major bump, from 15.0.1 to 16.0.0, but i do agree it should had been mentioned in the release notes. I have updated the notes and will make sure to take care of this in future releases 🙏