v1.2.1
A follow-up to v1.2.0, which made an empty env: reference invalidate its environment file. The TUI can now recover from a broken environment file and refuses to send requests until an environment loads successfully.
Fixed
Recover from a broken environment file
The TUI now starts when an environment file has parse or content errors. It shows the error in a modal and status bar, displays ENV: not loaded, and blocks requests.
Fix and save the file with Ctrl+S to reload it and reapply the environment selected at launch, including --env and --env-group. Missing or unreadable files remain fatal because there is nothing Resterm can open and repair. resterm run and other headless execution are unchanged: any environment-file error stops the run.
Environment edits now take effect
Saving the environment file in Resterm, reloading it from disk, or changing it externally while it is open now rebuilds the active environment. Previously, the editor could show new values while requests continued using the endpoints and credentials loaded at startup.
Also fixed
- A workspace change preserves a broken pinned
--env-file, so it cannot silently unblock requests. Ctrl+Ereports that the environment file failed to load instead of saying no environments are configured.- If an edit breaks a previously loaded environment file, Resterm reports the error and keeps using the last successfully loaded environment.