Get comments for questions and answers

[c-schuhmann]

Like mentioned in #32.

[c-schuhmann]

Error: Timeout of 2000ms exceeded.
I think we should set a higher timeout, because it timed out multiple times on my machine, even on methods I left untouched.
What do you think?

[Trott]

Error: Timeout of 2000ms exceeded.
I think we should set a higher timeout, because it timed out multiple times on my machine, even on methods I left untouched.
What do you think?

The problem usually isn't the timeout. That's an artifact of the test framework. The problem is usually that the endpoint is reporting too much usage and a "you're throttled, try again later" JSON payload. At least, that's what I've seen in a number of situations.

So there are two things to do here:

1. Replace the actual calls to StackExchange with calls mocked by nock.
2. Improve the error reporting by the test tools.

If we do those things and there's still evidence that the timeout needs to be increased, then hey, OK. I've upped the timeout to 30 seconds though and still seen these errors, and then found out they weren't really timeouts when I dug in.

All that said, something that allows you to specify a timeout on the command line when you run the tests locally would be fine to do immediately if that would be useful.

[Trott]

This is fine, but FYI you can add .vscode to your .gitignore file in your home directory (assuming you develop projects in subdirectories of your home directory) and it will apply to everything everywhere and you'll never need to add this to a project .gitignore file again.

[c-schuhmann]

Good point, I actually didn't knew that!

[Trott]

LGTM. Optional addition: You can add an example in the README file. Or not!

[Trott]

Landed and published in 1.3.0! 🎉