-
Notifications
You must be signed in to change notification settings - Fork 146
Open
Labels
area:documentationRelating to the documentationRelating to the documentationarea:examplesRelating to the examplesRelating to the examplesdifficulty:easyA simple task appropriate for newcomers to the codebaseA simple task appropriate for newcomers to the codebasegood first issueGood for newcomersGood for newcomerstype:chorePart of regular code upkeepPart of regular code upkeep
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
Description
To create an example following the new format to showcase how a service can be both a consumer and provider.
A hypothetical example within our standard user services:
sequenceDiagram
participant User as User (Consumer)
participant UserService as User Service (Consumer & Provider)
participant AuthService as Auth Service (Provider)
User->>UserService: Request to create account
UserService->>AuthService: Validate credentials (Consumer)
AuthService-->>UserService: Credentials valid/invalid
UserService-->>User: Account created response
Motivation
It is quite common for a service to be both a consumer and provider, but the usual Pact examples really only show them as being one or the other.
Have you tried building it?
No response
Self-service
- I'd be willing to contribute this feature to Pact Python myself.
Metadata
Metadata
Assignees
Labels
area:documentationRelating to the documentationRelating to the documentationarea:examplesRelating to the examplesRelating to the examplesdifficulty:easyA simple task appropriate for newcomers to the codebaseA simple task appropriate for newcomers to the codebasegood first issueGood for newcomersGood for newcomerstype:chorePart of regular code upkeepPart of regular code upkeep
Type
Projects
Status
🚀 To-Do