trilogy-data / trilogy-data/pytrilogy
Pseudonym Parsing Improvements
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 3
- Avg merge
- 7h 18m
- Merged PRs (30d)
- 43
Description
Problem Statement
Pseudonyms aren't flexible enough to optimize for all future cases, which might result in more costly discovery or inefficient query shapes.
Proposed Solution
We should capture enough information at merge time to know when a psuedonym is complete - eg a struct member access that is also a key - vs a partial, such as from a merge.
We may want to split merge handling and direct pseudonym handling entirely to some degree.
Alternatives Considered
Additional Context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. First locate pseudonym and merge handling in the Python codebase, then clarify how complete versus partial pseudonyms should be represented and define tests for struct-member, key, and merge cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100