Consider how to optionally wrap fragments
Open
Nobody has claimed this yet.
design
fragments
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
Fragments are currently concatenation together without any form of wrapper - which means the model can't tell one fragment from another.
Should we address that in core or via plugins? Maybe a --wf/--wrap-fragments option?
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
No files, tests, or entry points are named. Start by locating how fragments are concatenated and how command-line options and plugins handle them, then determine whether wrapping belongs in core or a plugin. Done should include an agreed wrapper interface, implementation, and tests covering wrapped and unwrapped fragments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100