News¶
1.0.0-rc1 • Outcome and documentation
General
- Added the description of each projection in its documentation (#45, !37)
- Added information on how to use the project (#45, !37)
State
- Removed the 'reporter' progress of the slice builder, avoiding the context creation on each call (#3bad6da0, !36)
- Renamed Slice to Outcome (#49, !38)
- Created ProgressiveOutcome, which combines an Outcome with a Progression (#47, #49, !36, !38)
Cache
Backbone
Spine
1.0.0 • Stabilization of Logger, State, Cache and Backbone
The projects Logger, State, Cache and Backbone are now reaching stable status. All future API changes will go through proper depreciation cycles.
Spine (and its related projects, Spine-Ktor, etc) are still experimental.
0.5.2 • Endpoint advertisement
The library is getting closer to the 1.0 release! The next steps are to add more documentation.
Spine for Ktor
Build
- Faster CI (!34)
0.5.1 • Easier caching and failure management cohesion
State
- Cleaned up the 'valueOrThrow', 'valueOrNull', 'requestValueOrThrow()', 'firstValueOrNull()' methods (#40, !31)
- Callback implementation of
ProgressionReporter
(#39, !32) - Removed the Identifier interface (#41, !33)
Spine
Deployment
- Fixed a Dokka memory exaustion bug which made the documentation fail to generate (!30)
- GitLab Pages now displays the documentation for the latest tag, and not for the 'main' branch (#14, !29)
- Optimize GitLab CI pipeline usage (!30)
0.5.0 • State rewrite
Instead of using our own State type, we use Arrow's Either. We also decouple Progression from State.
0.4.4 • Sub-route deletion, URL character list expansion
Spine
- It is now possible to create deletion operation on sub-routes (#32, !25)
- Endpoints are now allowed to be composed of almost all characters, the API implementation is responsible for URL-encoding etc (#37, !24)