Klaus Alfert

See #3, #4 and #5. There are/were some rudiments in my codebase. It requires to re-implement a big part of proper.

Back in time - if I remember right and 3 years is a lot of time - I recognised that parsing/handling of more interesting types in Proper was done on...

I like the approach 5 with `default_opts`. As already discussed somewhere else, we should provide a general approach to collect the options. Default options cry for the Application Environment, since...

> might not work when running in async mode. I need to be more precise, default options is the wrong name. What I meant are global configurations, which are independent...

A test case should never modify the app environment since it is generally not well defined when the values of the environment are read again, since it is used for...

Hmm, let me try to explain my thoughts. What I understand from your remarks, that we really need a good semantics how the various levels are detected and how they...

Can you provide a little more context? I would assume (w/o knowing anything about Oban) that there is a problem with clashing names of macros.

That's a nice example how to make an intrinsic stateful situation quasi stateless. And that approach immediately translates into similar approaches outside of stateful testing (`cmds

Sorry for the late delay, but if you want to assert a match, I would suppose to use `match?`: ```elixir property "returns a map" do forall i

The behaviour is exactly how it is implemented :-) It is the simple situation where you have a function with two expressions in the body. Only the latter will be...