Error number 3217 is reused for two errors

[psfinaki]

Inspired by this issue.

3217,packageManagerError,"%s"
3217,notAFunctionButMaybeIndexerErrorCode,""

Such cases might bring extra inconvenience to things like code fixes and tooling in general.

[smoothdeveloper]

I wanted to suggest putting a unit test in place, that would contain the list of exceptions (with a reason), and making CI fail when new duplicates are added.

Plus something like find.next.id.fsx

[psfinaki]

@smoothdeveloper yes, this sounds reasonable.

[github-actions]

🤖 This is an automated response from Repo Assist.

This issue appears to have been fixed. In the current codebase, packageManagerError has been renumbered from 3217 to 999 — it now appears as:

999,packageManagerError,"%s"
```

…while `notAFunctionButMaybeIndexerErrorCode` remains at `3217`:

```
3217,notAFunctionButMaybeIndexerErrorCode,""

The duplicate error number 3217 that was the subject of this issue no longer exists. This issue may be safe to close.

Generated by Repo Assist · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@9135cdfde26838a01779aa966628308404ec1f02