fd556525a8
* refactor(color): Use enum class for color type
* Add testcases for tag parser
* Make tag parser a pull-style parser
Being able to parse single elements at a time gives us more fine-grained
error messages, we can also parse as much as possible and only stop
after an exception.
* fix(color): Parser did not check for invalid chars
* tag parser: First full implementation
* tag parser: Fix remaining failing tests
* tag parser: Replace old parser
* tag parser: Treat alignment as formatting tag
Makes the structure less complex and the alignment tags really are
formatting tags, they are structurally no different from the %{R} tag.
* tag parser: Cleanup type definitions
All type definitions for tags now live in tags/types.hpp, the parser.hpp
only contains the definitions necessary for actually calling the parser,
this shouldn't be included in many places (only places that actually do
parsing). But many places need the definitions for the tags themselves.
* Rename components/parser to tags/dispatch
* tag parser: Cleanup
* Add changelog
53 lines
2.6 KiB
Markdown
53 lines
2.6 KiB
Markdown
# Changelog
|
|
All notable changes to this project will be documented in this file.
|
|
Each release should have the following subsections, if entries exist, in the
|
|
given order: `Breaking`, `Build`, `Deprecated`, `Removed`, `Added`, `Changed`,
|
|
`Fixed`, `Security`.
|
|
|
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
|
## [Unreleased]
|
|
### Breaking
|
|
- We rewrote our tag parser. This shouldn't break anything, if you experience
|
|
any problems, please let us know.
|
|
The new parser now gives errors for certain invalid tags where the old parser
|
|
would just silently ignore them. Adding extra text to the end of a valid tag
|
|
now produces an error. For example, tags like `%{T-a}`, `%{T2abc}`, `%{rfoo}`,
|
|
and others will now start producing errors.
|
|
This does not affect you unless you are producing your own formatting tags
|
|
(for example in a script) and you are using one of these invalid tags.
|
|
|
|
### Added
|
|
- Warn states for the cpu, memory, fs, and battery modules.
|
|
([`#570`](https://github.com/polybar/polybar/issues/570),
|
|
[`#956`](https://github.com/polybar/polybar/issues/956),
|
|
[`#1871`](https://github.com/polybar/polybar/issues/1871),
|
|
[`#2141`](https://github.com/polybar/polybar/issues/2141))
|
|
- `internal/battery`: `format-low`, `label-low`, `animation-low`, `low-at =
|
|
10`.
|
|
- `internal/cpu`: `format-warn`, `label-warn`, `warn-percentage = 80`
|
|
- `internal/fs`: `format-warn`, `label-warn`, `warn-percentage = 90`
|
|
- `internal/memory`: `format-warn`, `label-warn`, `warn-percentage = 90`
|
|
- Per-corner corner radius with `radius-{bottom,top}-{left,right}`
|
|
([`#2294`](https://github.com/polybar/polybar/issues/2294))
|
|
- `internal/network`: `speed-unit = B/s` can be used to customize how network
|
|
speeds are displayed.
|
|
|
|
### Changed
|
|
- Slight changes to the value ranges the different ramp levels are responsible
|
|
for in the cpu, memory, fs, and battery modules. The first and last level are
|
|
only used for everything at or below and at and above the edges of the value
|
|
range, respectively. The other levels are evenly distributed over the value
|
|
range as before.
|
|
- `custom/script`: `interval` now defaults to 0 if `tail = true` as per the
|
|
documentation.
|
|
- `internal/network`:
|
|
- Increased precision for upload and download speeds: 0 decimal places for
|
|
KB/s (as before), 1 for MB/s and 2 for GB/s.
|
|
|
|
### Fixed
|
|
- Parser error if click command contained `}`
|
|
([`#2040`](https://github.com/polybar/polybar/issues/2040))
|
|
|
|
[Unreleased]: https://github.com/polybar/polybar/compare/3.5.2...HEAD
|