Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidelines regarding rendered interaction description #254

Closed
1 task done
FantasticFiasco opened this issue Nov 26, 2018 · 1 comment
Closed
1 task done

Guidelines regarding rendered interaction description #254

FantasticFiasco opened this issue Nov 26, 2018 · 1 comment

Comments

@FantasticFiasco
Copy link

Pre issue-raising checklist

I have already

  • Upgraded to the latest Pact Broker

Software versions

  • pact-broker docker version: 2.27.6-1
  • OS: Windows 10

Expected behaviour

The interaction description should be rendered as it is formatted in the pact definition.

Actual behaviour

I'm wondering whether I, without knowing it, am violating a description convention since my interactions are formatted kind of funny. The broker sometimes capitalize the description and sometimes not, and I don't know when and why.

Steps to reproduce

Publish the following pact:

{
  "consumer": {
    "name": "Foo"
  },
  "provider": {
    "name": "Bar"
  },
  "interactions": [
    {
      "description" : "GET /something",
      "providerState": null,
      "request": {
        "method": "get",
        "path" : "/something"
      },
      "response": {
        "status": 200,
        "body" : "something"
      }
    }
  ]
}

and navigate to http://localhost/pacts/provider/Bar/consumer/Foo/latest to see the Upon receiving gET /something from Foo, with as interaction description.

@bethesque
Copy link
Member

When I write it, the description usually starts with "a request for". The code is not smart enough to downcase the whole first word.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants