BREAKING CHANGE: exit segment is now called status segment.
The exit keyword is now deprecated and will be removed in a future
release. Please use the status keyword instead:
```diff
"segments": {
{
- "type": "exit"
+ "type": "status"
}
}
```
Additionally, the status segment configuration has changed to support
$PIPESTATUS. You can include a status template to customize the
rendering of each individual status code (supported in fish, zsh and
bash).
```json
"segments": {
{
"type": "status",
"properties": {
"status_template": "{{ if gt .Code 0 }}\uf071{{ else }}\uf00c{{ end }}",
"status_separator": " "
}
}
}
```
In case no $PIPESTATUS is available, the status segment will fall back
to the exit code of the last command using the status template
for rendering.
The `{{ .Meaning }}` property has been marked as deprecated and can be
replaced with `{{ reason .Code }}`, allowing it to be reused in
cross segment templates.
resolves#4070
BREAKING CHANGE: adjusts the way some segment work for templates.
Mapping the var names as following will resolve the issue.
- session/title/general purpose
- .Host -> .HostName
- .User -> .UserName
- az
- .UserName -> .Name
- kubectl
- .UserName -> .User
this deprecates the "newline" block and favours using the newline
property on the Block component. For backwards compatibility we'll
keep recognizing the newline block for the time being.
resolves#607
