RFC: nameparser 2.0 — a new core API#285
Open
derek73 wants to merge 1 commit into
Open
Conversation
The design document for 2.0: a new immutable core API (parse() -> ParsedName, Lexicon/Policy configuration) alongside HumanName as a compatibility layer through 2.x. Covers the compatibility promise, the new API, migration mechanics, locale plans, rejected alternatives, and the feedback questions. Discussion: #284. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Repository owner
deleted a comment from
codecov-commenter
Jul 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: if you only use
HumanNameand never customize configuration, 2.0 should be a non-event for you — but it's cool and we'd love your feedback anyway.This PR adds a design document:
docs/design/nameparser-2.0-rfc.md, the RFC for nameparser 2.0 — a new immutable core API (parse()→ParsedName,Lexicon/Policyconfiguration) alongsideHumanName, which continues to work as a compatibility layer through all of 2.x.This PR is documentation-only and will stay that way. Implementation happens on separate branches with their own PRs; what lands here are amendments to the design as implementation and feedback teach us things.
How to review:
==? subclass? mutateCONSTANTSlate? custom regexes?) → the discussion issue: nameparser 2.0: a new core API, with full compatibility through 2.x — direction and feedback #284.There is no comment deadline. The PR stays open while the design settles; merging it marks the design stable (likely around the first 2.0 alpha) and keeps the document in
docs/design/as the standing record. The design may change in response to comments right up to that point — that's what this is for.🤖 Generated with Claude Code