fix: device attributes type

[soberm]

Description of changes

The runtime structure returned by fetchDevices() contains device attributes as a plain object with keys like device_status, device_name, and last_ip_used, but the TypeScript definition incorrectly defines attributes as AuthUserAttribute<UserAttributeKey> (a single object with attributeKey and value properties). This PR updates the type for device attributes.

Issue #, if available

#14517

Description of how you validated changes

Manually verified that the types are correct.

Checklist

• PR description included
• yarn test passes
• Unit Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

• Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
• New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[kturczyski-lz]

Thanks a lot @soberm for looking into this so quickly. It looks like this may not be the full list of predefined attributes (based on the existing type). There also seem to be some custom attributes involved. Could you double check this with the reviewers?

amplify-js/packages/auth/src/providers/cognito/types/models.ts

Line 57 in a196b0c

export type UserAttributeKey = AuthStandardAttributeKey | CustomAttribute;

amplify-js/packages/core/src/singleton/Auth/types.ts

Line 81 in a196b0c

export type AuthStandardAttributeKey =

amplify-js/packages/auth/src/providers/cognito/types/models.ts

Line 68 in a196b0c

export type CustomAttribute = string & NonNullable<unknown>;

[soberm]

Hi @kturczyski-lz, will double check but the previous type mistakenly used UserAttributes and not DeviceAttributes which are different.

[kturczyski-lz]

Ahh, yeah, sorry, I actually see only those 3 keys in the result. I assumed the old type wasn’t simply ported to the new structure.