Let AspNetCoreWire support different timeout values

DFU398 commented 4 years ago

Please check if the PR fulfills these requirements

[x] I made sure that my code builds (VisualStudio & cake script: build.ps1)
[x] I merged the master into this branch before pushing
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

What is the new behavior?

closes #30

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications

Other information

DFU398 commented 4 years ago

don't merge this just yet, i want to add a few lines about IAspHttpClient and how/why to use it to the readme while i'm at it, but i wont have time for the next hour or so

There should be a WIP Label for PRs

Edit: Done.

Meerownymous commented 4 years ago

@dfu398 okay, I‘ll wait. I will add a wip label - we also soon will have an updated script to create our labels so they are consistent.

icarus-consulting / Yaapii.Http

Let AspNetCoreWire support different timeout values #31