Repository navigation
Releases: Quilt4/quilt4net-dotnet
Release list
v1.0.30
What's Changed
- feat(issue): a limit on the issue filter, so the roadmap draws only the first N issues in the order by @husiki in #229
New Contributors
Full Changelog: 1.0.29...1.0.30
v1.0.29
What's Changed
- feat(issue): a waiting flag on issues, and Blocked / Waiting / Ready on the issue filter by @poxet in #228
Full Changelog: 1.0.28...1.0.29
v1.0.28
What's Changed
- feat(blazor): Quilt4NetPanel - a tab per Quilt4Net service, each also a component of its own by @poxet in #227
Full Changelog: 1.0.27...1.0.28
v1.0.27
v1.0.26
What's Changed
- feat: notification client by @poxet in #217
- feat: heartbeat reporting with capabilities by @poxet in #218
- feat: heartbeat reporting with capabilities by @poxet in #219
- fix: report failed issue and release-note calls by the server's own explanation by @poxet in #220
- fix: switched-off features answer 403 as a warning, with the server's sentence by @poxet in #221
- chore(deps): update NuGet packages; OpenTelemetry 1.20 log record tests by @poxet in #222
- docs: open the README with what Quilt4Net does by @poxet in #223
Full Changelog: 1.0.25...1.0.26
v1.0.25
Content: uncached keys are fetched in batches. Keys the cache does not hold are now collected for a short window (ContentOptions.BatchWindow, 20 ms by default) and sent as one request (at most BatchMaxSize, 100 keys), instead of one request per key. A page full of new keys costs one call. A lone key still goes as a normal single request, and a server without the batch endpoint is detected and asked key by key, so this works against any server version. Set BatchWindow = TimeSpan.Zero to turn it off.
What's Changed
Full Changelog: 1.0.24...1.0.25
v1.0.24
What's Changed
Full Changelog: 1.0.23...1.0.24
v1.0.23
Content: the selected language from the first paint. When a key is not cached yet, the client used to show the default (usually English) text until the server answered, even when the caller had supplied the translation for the selected language. It now shows the supplied translation straight away, for the selected language, in every fallback path (the 200 ms materialization wait, timeouts, errors and failed background refreshes). Nothing to change in your code; translations you already pass in Translations are used.
What's Changed
- fix(content): show the supplied translation, not the default, while the server has not answered by @poxet in #211
Full Changelog: 1.0.22...1.0.23
v1.0.22
What's Changed
Full Changelog: 1.0.21...1.0.22
v1.0.21
What's Changed
Full Changelog: 1.0.20...1.0.21