---
url: >-
  https://canary.warp-drive.io/api/@warp-drive/core/build-config/deprecations/variables/DEPRECATE_NON_STRICT_ID.md
description: >-
  Deprecation flag for legacy support of numeric resource IDs that are coerced
  to strings; set it to `false` once resolved to strip that support.
---

#  DEPRECATE\_NON\_STRICT\_ID 

```ts
const DEPRECATE_NON_STRICT_ID: boolean;
```

Defined in: [warp-drive-packages/build-config/src/deprecations.ts:193](https://github.com/warp-drive-data/warp-drive/blob/48dc0d277b98008082669dadc6a52e5c5682ef8e/warp-drive-packages/build-config/src/deprecations.ts#L193)

Currently, WarpDrive expects that the `id` property associated with
a resource is a string.

However, for legacy support in many locations we would accept a number
which would then immediately be coerced into a string.

We are deprecating this legacy support for numeric IDs.

The goal is that in the future, you will be able to use any ID format
so long as everywhere you refer to the ID you use the same format.

However, for identifiers we will always use string IDs and so any
custom identifier configuration should provide a string ID.

## Until

6.0