Provide a better way to resolve paths
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
The issue names no files, tests, or entry points. Start by locating the current manual path-resolution logic for dependent maps and trace how those paths are consumed. Done means dependent maps expose pre-resolved paths, with the existing behavior covered by relevant tests.
Written by the indexing model from the issue text.
Description
Right now path resolution for the dependent maps is manual. It would be nice to provide pre-resolved versions.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 23h 15m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from simonsobs/mapcat
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
wafers not attribute Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in simonsobs/mapcat
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100