Create message Pact docs
Maintainers usually reply within 9 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by locating the existing consumer and provider documentation sections and review how they are structured. Add a new section covering both synchronous and asynchronous message verification with Pact Python; done means the documentation builds successfully and explains both workflows clearly.
Written by the indexing model from the issue text.
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
Description
To add a new section to the docs documenting how Pact Python can be used to verify messages, both synchronous and asynchronous.
The docs should build on top of the existing consumer and provider docs.
Motivation
To help with the adoption of message verification using Pact Python
Have you tried building it?
No response
Self-service
- I'd be willing to contribute this feature to Pact Python myself.
- Dominant language
- Python
- Stars
- 689
- Forks
- 147
- Avg merge
- 8d 11h
- Merged PRs (30d)
- 27
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a 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 pact-foundation/pact-python
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
Post v3 tracking issueMay be free again @JP-Ellis claimed this 412 days ago, and no pull request is open. Opentype:tracking
pact-foundation/pact-python#1272 · 1 assignee ·
Maintainers usually reply within 9 days
-
area:documentation difficulty:easy type:chore
Difficulty 3/5 1-2 days Newbie friendliness 48/100
pact-foundation/pact-python#1267 ·
Maintainers usually reply within 9 days
-
(V3) Verifying a contract with a missing content field is always successful when it should errorPossibly taken @JP-Ellis claimed this 412 days ago. Openarea:core type:bug
pact-foundation/pact-python#1103 · 5 comments · 1 assignee ·
Maintainers usually reply within 9 days
-
Add a complete gRPC examplePossibly taken @JP-Ellis claimed this 514 days ago. Openarea:core area:documentation area:examples difficulty:medium smartbear-supported type:chore
pact-foundation/pact-python#1092 · 1 comment · 1 assignee ·
Maintainers usually reply within 9 days
All issues in pact-foundation/pact-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
backend/local comp/tools P2 tool/terminal type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#158788 ·
Maintainers usually reply within 1 day