Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

And maybe dates formatted in different ways.

My usecase is that I might receive or parse "randomly" formatted dates, and they should all be parseable and saved to the db in a specific format.

Testing broadly for multiple possible formatted dates would be ideal.

This could be done to the JVM as it has it's own DateTimeFormatter, but other platforms might also use this.

It would be nice to start building Pester on PowerShell 7 as well to see if it is compatible and keep it that way. To achieve that we need to research on which build servers v7 is already available. Right now we are building on TravisCI (Linux and MacOS), on AppVeyor (PowerShell 4+) and AzureDevOps (PowerShell 2&3).

Not sure if the build task needs to run on all three platforms, but it would be

Summary

ShouldContainOnly is used in a few places where we know what kind of elements we are dealing with, in this case instead of using the term element we could use a more descriptive name.

Example

Spliterator<?> actual = createSpliterator(SORTED | ORDERED);
spliterators.assertHasOnlyCharacteristics(INFO, actual, DISTINCT, SORTED);

fails with this error

Feature Request

Description:
API for Date matchers. Some matchers are inspired by Jasmine Matchers.

Possible solution:

Jasmine-like matchers:

expect(date).toBeDate(); // Matcher added
expect(date).toBeValidDate();  // Matcher added

expect(date).toBeAfter(otherDate); // Matcher added
expect(date).toBeBefore(otherDa

Here is the example of data file(test_data_json.json) i am using to drive through my test file to produce messages into kafka:

{"key":"111","value":{"id":121,"name":"Jey"},"headers": {"batchId": "${$.initiate_batch.response.body.id}","test": "tester"}}
{"key":"222","value":{"id":122,"name":"Krep"},"headers": {"batchId": "${$.initiate_batch.response.body.id}","test": "tester"}}

Not

Is your feature request related to a problem? Please describe.

Since dropping python 3.5 #142 the pandera code-base can now use f-string formatting for conciseness and ✨ elegance ✨

Describe the solution you'd like

• replace all instances of '%s' formatting with f"{}" string formatting

Normally, the "to be truthy" assertion does not take any value as it simply asserts that a subject can be coerced to a boolean true (in the case of "to be falsy" it is coercion to boolean false).

It seems that early on these assertions inherited an optional form where a custom message can be supplied as their argument - this was likely inspired by earlier assertions frameworks (assert on node

Non-Code related feature

Atrium is currently using dokka 0.9.8 via the tutteli-dokka plugin.
We would like to update to dokka 1.4.10

Following the things we need to do:

• remove classpath "ch.tutteli:tutteli-gradle-dokka:$tutteli_plugins_version" from build.gradle
• configure the new dokka plugin instead. You don't have to bother what was configured before, you can start from