I think RSpec should provide around(:context)/around(:all). Not because of any particular use case, but simply for API consistency. It's much simpler to tell users "there are 3 kinds of hooks (before, after and around) and each can be used with any of 3 scopes (example, context and suite)". Having some kinds of hooks work with only some kinds of scopes makes the API inconsistent and forces us to add special case code to emit warnings and also write extra documentation for this fact.

Epics can contain both issues and epics as children

This kind of error handling does express error state (either via HTTP 500 or by the top-level "errors" key), but it doesn’t take advantage of GraphQL’s type system and can only express one error at a time.

The primary branch in git can have any name by design.

To set multiple cookies in a single set of response headers, you can return an array:

The guard name defaults to default and can be set via name:. This allows having multiple guards.

# Yes, you can use lambdas as steps, too! step ->(ctx, params:, **) { params.is_a?(Hash) }

A nested activity doesn’t have to have two ends, only.

Please note that I/O works for both “simple” tasks as well as nested activities.

Note that it's perfectly fine to add errors during execution. Not all errors have to come from type checking or validation.

*initialize* also supports passing resources (also attributes if you would # like to) manually

It must be called during the component's initialisation (but doesn't need to live inside the component; it can be called from an external module).

Fixes #1037 allow slotted components via making <Component> <Inner slot="foo" /> </Component> as a sugar syntax for <Component> <svelte:fragment slot="foo"> <Inner /> </svelte:fragment> </Component>

It's possible to have multiple event listeners for the same event

More than one subscriber can subscribe to the same field.