Create processing rules section
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the discussion linked from the issue, especially the notes about handling the credential_types array, and check the current specification text. The issue says this work should wait until other specification changes are stable; define the processing rules section only once those changes have settled, with the relevant behavior stated in the spec.
Written by the indexing model from the issue text.
Description
As per https://github.com/openid/dchp/pull/61#discussion_r4185068111 - there are some things that spec should probably say (like how the credential_types array is handled) that would sit best in a processing rules section - though it's probably not worth working on that till we have some of the other changes to the spec stable.
- Dominant language
- Python
- Stars
- 18
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 openid/dchp
-
naming
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
-
CDDL/prose text misalignment + editorial issuesPossibly taken @c2bo claimed this 19 days ago. Open
Difficulty 2/5 Half a day Newbie friendliness 22/100
-
Difficulty 3/5 Half a day Newbie friendliness 15/100
Similar issues
-
cost:cheap practicality:seen-in-the-wild severity:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fairagro/m4.2_advanced_middleware_api#620 ·
Maintainers usually reply within 1 day
-
area:security effort:S priority:P2 provider:local-libvirt status:ready type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
randomparity/kdive#3495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/markitdown#2820 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days