Support full string ids #53
Open
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.
π€ AI-Powered Solution
This pull request implements full string ID support as requested in issue #11.
π Issue Reference
Fixes #11
β Implementation Details
Core Enhancement:
TryParseLinkIdfunction to support string aliases alongside existing numeric ID parsingNamedLinksDecoratorfor alias resolutionAdvancedMixedQueryProcessorto use the new string-aware parsingKey Features:
person,name,valueinstead of numeric IDsExample Usage:
π§ͺ Testing
ποΈ Architecture
The implementation leverages the existing
NamedLinksDecoratorinfrastructure:.names.linksfile alongside main databaseNamify()function in Program.cs already converts numeric IDs back to names in outputThis provides the key-value store functionality requested in the issue, where string aliases effectively serve as keys that map to link relationships, giving users a Redis-like interface for link manipulation.
π€ Generated with Claude Code