Add pattern support for `about_resource` field?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start with the ABOUT spec and the discussion in PR #539, then identify where about_resource is defined and validated in this repository. Decide whether patterns belong in a new deployed-side field or the existing field; done means the chosen spec change and its toolkit impact are documented and agreed.
Written by the indexing model from the issue text.
Description
Now we are using patterns to map to deployed resource paths, and this is also different from the about_resource field in the ABOUT spec as this is resources in the deployed side, and not present side-by-side in the devel codebase. We are currently using about_resource temporarily to have these patterns, until this spec change is accepted. But this is incorrect both because of the above reason, and that the about_resource spec does not support patterns for now.
https://github.com/aboutcode-org/aboutcode-toolkit/pull/539#issuecomment-1782270839
@pombredanne @AyanSinhaMahapatra
What’s the current status, and what plan/change needs to be made?
At present, the about_resource field is designed to reference a single resource (file or directory) at a time.
Should we introduce a new field to support patterns for about_resource on the deployed side, or should we extend the existing about_resource field to include pattern support
- Dominant language
- Python
- Stars
- 100
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from aboutcode-org/aboutcode-toolkit
-
Update PURLDB with all ABCTK releasesMay be free again @pombredanne claimed this 614 days ago, and no pull request is open. OpenImportant needs design
aboutcode-org/aboutcode-toolkit#582 · 2 comments · 3 assignees ·
-
Enhance `about_resource` to reference multiple files.May be free again @chinyeungli claimed this 266 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#566 · 2 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Create test file with a few hundred itemsMay be free again @DennisClark claimed this 1731 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#491 · 2 assignees ·
-
Clean up / Organize codeMay be free again @sahil-MK2 claimed this 1750 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#483 · 1 comment · 2 assignees ·
All issues in aboutcode-org/aboutcode-toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day