Ravi van Rooijen

It looks like this is still (or again) broken. When building https://github.com/HoldYourWaffle/NBT/commit/404d5d83bdd26821cc3827a042e25f9f7d943e6d today Jitpack tries to use Java 8 ([log](https://jitpack.io/com/github/HoldYourWaffle/NBT/404d5d83bd/build.log)). However, the build of https://github.com/Querz/NBT/commit/404d5d83bdd26821cc3827a042e25f9f7d943e6d from May 10th correctly used...

After some more testing it seems that for JDK 13 and later the `jdk` option in `jitpack.yml` no longer works properly. The `before_install` "workaround" mentioned in the [documentation](https://jitpack.io/docs/BUILDING/#java-version) seems to...

I think GitHub is having a bad day today... I think everything is set up as it should now though 🤔

Although, that syntax might be a mess to parse due to the absence of overloads in JavaScript. Perhaps something like this would be easier: ```js itParam.describe(*describe name*, *test name*, [...

I finally managed to get the type definitions right, again with a manual and automatic variant.

I just noticed that everything (defintions & code) concerning `retries` is probably wrong. I have never actually used that functionality before, and it looks like there's a mistake in the...

After some investigation I can only conclude that a couple of things just don't seem to add up. 1. `it.retries(x)` (and thus `itParam.retries`) is *valid*, but errors at runtime -...

Unfortunately it looks like this means that the automatic system won't work, because (as far as I know) there's no way in JS to determine if a function should be...

Just like #15 this might introduce parsing difficulties, although I think it's easier to differentiate between a `string` or `array` as the first parameter. To avoid this complication the syntax...

We could even eliminate the inner-arrays like so: ```js itParam.named([ 'descriptive name for a', a, 'descriptive name for b', b ], function(value) { // ... }) ``` And "split" the...