Add a 'readme' to the nuget package about pact-net

[neilcampbell]

Hey @sawilde. Do you see this as a physical file within the nuget package? Or would a simple link on https://www.nuget.org/packages/PactNet/ to the readme suffice?

[sawilde]

If you add it to the nuget package you can get it to show in visual studio when the package is first installed.

It can then provide links etc to how to get started. i.e. I didn't realize the headers were part of the verification rather than the matching.

By they way I may use your mocking tool to test the MYOB SDK as it looks much nicer then what I currently have.

---

From: Neil Campbellmailto:[email protected]
Sent: ‎7/‎10/‎2014 4:31 PM
To: SEEK-Jobs/pact-netmailto:[email protected]
Cc: Shaun Wildemailto:[email protected]
Subject: Re: [pact-net] Add a 'readme' to the nuget package (#24)

Hey @sawilde. Do you see this as a physical file within the nuget package? Or would a simple link on https://www.nuget.org/packages/PactNet/ to the readme suffice?

---

Reply to this email directly or view it on GitHub:
#24 (comment)

[neilcampbell]

I'm not a massive fan of the show readme on install approach. A lot of the time, I know how a library works and I am just installing it in a new project, but yeah it certainly helps on the first install. I'm going to see what others think on this one.

With regards to the How to get started comment, I would love to hear all the things that bit you, as I know some of items are not documented in the Pact-Net readme. The one you mentioned is actually a really good example, it is document in the Pact specification project, however most users will not read that.

[sawilde]

The sample you gave in the readme.md was useful to getting started though I don't use xunit on my project (I did in the spike but will probably change it to nunit). Though it led me down a few wrong paths especially as it throws a 500 when you get the mock (expectation) wrong. I tried a lot of things to get it to work as I couldn't determine what was par of the expectation and what was part of the verification. By the way I think my next suggestion may be to add the doc xml file (I know people don't like code comments - but the doc xml file can be used to provide intellisense) again helps people get going quicker :)

Is there any way to see what has actually been set up so you can see what the expectation is i.e. url+query (I am assuming the query is part of the expectation) so when it goes pop you can look and go - "doh!"

[sawilde]

The readme can also be used to inform the user of breaking changes (hopefully none as you are awesome) and also help new users to the project when they upgrade it long after the original user has left the project that uses your package.