[GH-ISSUE #147] Better handling of invalid identifiers #46

Open
opened 2026-03-03 13:52:33 +03:00 by kerem · 0 comments
Owner

Originally created by @jehna on GitHub (Oct 6, 2024).
Original GitHub issue: https://github.com/jehna/humanify/issues/147

Originally from another thread:

instead of just forcing an invalid suggestion to be valid (with toIdentifier), we could detect that it's invalid (with isValidIdentifier) and then provide that feedback to the LLM, asking it to give a new suggestion; probably with some max retry limit; after which we could fall back to using the invalid suggestion run through toIdentifier, or log a warning and leave it un-renamed or similar.

Originally posted by @0xdevalias in https://github.com/jehna/humanify/issues/117#issuecomment-2381046017

Originally created by @jehna on GitHub (Oct 6, 2024). Original GitHub issue: https://github.com/jehna/humanify/issues/147 Originally from another thread: >> instead of just forcing an invalid suggestion to be valid (with toIdentifier), we could detect that it's invalid (with isValidIdentifier) and then provide that feedback to the LLM, asking it to give a new suggestion; probably with some max retry limit; after which we could fall back to using the invalid suggestion run through toIdentifier, or log a warning and leave it un-renamed or similar. > > _Originally posted by @0xdevalias in https://github.com/jehna/humanify/issues/117#issuecomment-2381046017_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/humanify#46
No description provided.