John A. De Goes

I am going to close this for now, as `Endpoint` is very well-developed and has lots of features related to this one.

Closing, please re-open if still relevant.

Now that we have a dependency on ZIO Schema anyway, we can introduce `decode` and `encode` methods to `QueryParams` which use ZIO Schema.

In ZIO 2, transitive fiber interruption is "instantaneous". This means a great grand-child can be interrupted before a parent finishes its winddown process. This is different behavior than earlier versions...

/bounty $25

I like it. FWIW, `or` is often called `race`, and `and` is equivalent to a function normally called `par`. See `purescript-parallel`, for example.

@afsalthaj and I discussed the following plan: 1. Remove everything in `zio.config._`, except for the documentation part, which can be retrofitted to work with `zio.Config` and `zio.ConfigProvider`. 2. Refactor integrations...

/bounty $100 for making it configurable in some nice and consistent way.

@camjo For `Type`, we only need to describe the type the user will receive after running the flow. So simple data structures like Scala's `Map` probably suffice. Internally, inside `LocalAnalyticsModule`,...

Btw, the `Type` stuff doesn't constrain our implementation _at all_. That's just for end-stage conversion.