fix(core): extend BaseKey to include number[] for UUID support

[devavijha]

Problem

BaseKey is currently typed as string | number. Some OpenAPI code generators represent UUID fields as number[] (byte arrays) in TypeScript. Users working with such types must cast their ID values to satisfy the BaseKey constraint:

useOne({ resource: "orders", id: uuidBytes as unknown as string })

This defeats TypeScript safety and produces confusing code.

See: #7403

Fix

Extend BaseKey from string | number to string | number | number[].

The change is additive. All existing usage of string and number IDs is unaffected.

// Before: required an explicit cast
useOne({ resource: "orders", id: uuidBytes as unknown as string })

// After: works without a cast
useOne({ resource: "orders", id: uuidBytes })

Files changed

• packages/core/src/contexts/data/types.ts — extends BaseKey union type
• packages/core/src/hooks/navigation/index.ts — fixes three encodeURIComponent(id) call sites that TypeScript correctly flags after the type extension; number[] is converted to a comma-separated string before encoding

TypeScript verification

Ran tsc --noEmit on packages/core before and after the change. The only remaining error is a pre-existing test file path issue present on main as well.

Closes #7403

[changeset-bot]

🦋 Changeset detected

Latest commit: f58324a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@refinedev/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[devavijha]

look into this...