From ab480e74417fe51172a7b97e644f15c3952aa16a Mon Sep 17 00:00:00 2001 From: Jonathan Daugherty Date: Thu, 8 Feb 2024 07:51:14 -0800 Subject: [PATCH] Add missing changelog entries for 6.0 --- CHANGELOG.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a6df38a..0d38f7a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -126,8 +126,14 @@ below. For people who want to write their own Vty platform package like IO ()`, for logging to the Vty log. * `Graphics.Vty.Config` now exposes `VtyUserConfig` instead of `Config`. Many of its fields were Unix-specific and were - consequently moved to the `UnixSettings` type in `vty-unix`. + consequently moved to the `UnixSettings` type in `vty-unix` and + given a `settings` prefix. This includes `outputFd`, `inputFd`, + `vmin`, `vtime`, and `termName`. * The `VtyUserConfig` type's fields got a `config` field name prefix. + * `inputForConfig` was moved to `vty-unix` as `buildInput` but + generally should not be needed and is exposed only for testing. + * `outputForConfig` was moved to `vty-unix` as `buildOutput` but + generally should not be needed and is exposed only for testing. * Behavior changes: * Since `vty` no longer implements `mkVty`, the Vty user configuration is no longer implicitly loaded by Vty-based applications.