mirror of
https://github.com/jtdaugherty/brick.git
synced 2024-12-28 16:34:45 +03:00
CHANGELOG: 1.0 edits
This commit is contained in:
parent
8772f5cc37
commit
6a41ba8216
@ -35,14 +35,13 @@ ticket](https://github.com/jtdaugherty/brick/issues/379).
|
|||||||
`handleEditorEvent` are now statically typed to be scoped to
|
`handleEditorEvent` are now statically typed to be scoped to
|
||||||
just the states they manage, so `zoom` from `microlens-mtl` must
|
just the states they manage, so `zoom` from `microlens-mtl` must
|
||||||
be used to invoke them. `Brick.Types` re-exports `zoom` for
|
be used to invoke them. `Brick.Types` re-exports `zoom` for
|
||||||
convenience.
|
convenience. `handleEventLensed` was removed from the API in lieu
|
||||||
|
of the new `zoom` behavior. Code that previously handled events
|
||||||
|
with `handleEventLensed s someLens someHandler e` is now just
|
||||||
|
written `zoom someLens $ someHandler e`.
|
||||||
* If an `EventM` block needs to operate on some state `s` that is
|
* If an `EventM` block needs to operate on some state `s` that is
|
||||||
not accessible via a lens into the application state, the `EventM`
|
not accessible via a lens into the application state, the `EventM`
|
||||||
block can be set up with `Brick.Types.nestEventM`.
|
block can be set up with `Brick.Types.nestEventM`.
|
||||||
* `handleEventLensed` was removed from the API in lieu of the new
|
|
||||||
`zoom` behavior. Code that previously handled events with
|
|
||||||
`handleEventLensed s someLens someHandler e` is now just written
|
|
||||||
`zoom someLens $ someHandler e`.
|
|
||||||
* Since `Next` was removed, control flow is now as follows:
|
* Since `Next` was removed, control flow is now as follows:
|
||||||
* Without any explicit specification, an `EventM` block always
|
* Without any explicit specification, an `EventM` block always
|
||||||
continues execution of the `brick` event loop when it finishes.
|
continues execution of the `brick` event loop when it finishes.
|
||||||
|
Loading…
Reference in New Issue
Block a user