Update documentation to better explain `@wip` tag
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Start with docs/source/development.rst and README.rst, then read gherkinize.py to understand how cel-spec test data becomes the features directory tree and receives @wip tags. Update the Development Tools explanation and add a README link; the complete feature-list page is already marked complete by #191. Done means both documentation paths clearly explain the flow and link correctly.
Written by the indexing model from the issue text.
Description
Three related changes to the documentation.
-
Update the Development Tools section (
docs/source/development.rst) to include an explanation of the@wiptag, and how the test data flows from cel-spec to thefeaturesdirectory tree with tags injected by thegherkinize.pytool. -
Add a link to this to the
README.rstto provide a clear path to show how@wiptags are injected into the tests. -
Add a page with the complete list of features, showing ✅ and ❌ for the features supported and the features marked
@wip. (It's not clear precisely how to do this. It might be an useful secondary output from thegherkinize.pytool.) Completed by #191
- Dominant language
- Python
- Stars
- 174
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
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 cloud-custodian/cel-python
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloud-custodian/cel-python#180 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
cloud-custodian/cel-python#194 ·
-
Refresh Features Opendependencies
cloud-custodian/cel-python#172 · 2 comments · 1 assignee ·
-
enhancement
cloud-custodian/cel-python#169 · 3 comments · 1 assignee ·
-
bug
cloud-custodian/cel-python#145 · 4 comments · 2 assignees ·
All issues in cloud-custodian/cel-python
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·