Skip to content

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

Closed
@hej2010

Description

@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?

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?

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions