Decision: accepted, not fixed. src/app/plugins/react-prism/PrismCode.tsx:69,74 key prism tokens by array index. Prism tokens are not unique within a line — repeated whitespace and punctuation produce identical token objects — so no stable key exists from the token content. Keying by token type plus index is the same key. The rule stays on and this issue stays open as the record of that decision.
Decision: accepted, not fixed. `src/app/plugins/react-prism/PrismCode.tsx:69,74` key prism tokens by array index. Prism tokens are not unique within a line — repeated whitespace and punctuation produce identical token objects — so no stable key exists from the token content. Keying by token type plus index is the same key. The rule stays on and this issue stays open as the record of that decision.
Superseded — the rule was turned off in eslint.config.js at 9b3956d8, and the five directives it made stale were deleted: DeviceVerification.tsx:139, PermissionGroups.tsx:1, Powers.tsx:1, ForumPostUploadField.tsx:183, RoomInput.tsx:638. No fix at the sites exists. Keying by the segment offset in the source text would be unique, but that is the same positional key computed a different way and only exists to satisfy the linter.
Superseded — the rule was turned off in `eslint.config.js` at `9b3956d8`, and the five directives it made stale were deleted: `DeviceVerification.tsx:139`, `PermissionGroups.tsx:1`, `Powers.tsx:1`, `ForumPostUploadField.tsx:183`, `RoomInput.tsx:638`. No fix at the sites exists. Keying by the segment offset in the source text would be unique, but that is the same positional key computed a different way and only exists to satisfy the linter.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
eslint/react/no-array-index-key: 2 violations.Decision: accepted, not fixed.
src/app/plugins/react-prism/PrismCode.tsx:69,74key prism tokens by array index. Prism tokens are not unique within a line — repeated whitespace and punctuation produce identical token objects — so no stable key exists from the token content. Keying by token type plus index is the same key. The rule stays on and this issue stays open as the record of that decision.Fixed in 9b3956d.
Superseded — the rule was turned off in
eslint.config.jsat9b3956d8, and the five directives it made stale were deleted:DeviceVerification.tsx:139,PermissionGroups.tsx:1,Powers.tsx:1,ForumPostUploadField.tsx:183,RoomInput.tsx:638. No fix at the sites exists. Keying by the segment offset in the source text would be unique, but that is the same positional key computed a different way and only exists to satisfy the linter.