Skip to content

Releases: Nouw/smoelenboek

[Patch] v4.0.21

27 Oct 17:46
Compare
Choose a tag to compare

Updated

  • VCP Information

Fixed

  • Minor bug with updating team information

[Patch] v4.0.18

12 Oct 19:26
Compare
Choose a tag to compare

Added

  • Team photos can now be synced with usvprotos.nl

[Patch] v4.0.17

10 Oct 12:54
Compare
Choose a tag to compare

Added

  • Category deletion

Fixed

  • Category deletion endpoint, it now catches the correct errors.
  • Updating category calls the correct endpoint

[Patch] v4.0.13

30 Sep 09:27
Compare
Choose a tag to compare

Fix

  • Match type women would not show 4 sets

[Patch] v4.0.12

20 Sep 19:02
Compare
Choose a tag to compare

Added

  • Anonymous users can now do predictions for Protototo
  • Participants of Protototo can now be exported to a excel sheet

Fixed

  • Bug where a user could not change their back number
  • Missed translations

[Patch] v4.0.11

15 Sep 19:53
Compare
Choose a tag to compare

Added

  • Frontend can now be run in Docker. sidenote: maybe check if it can be optimised, using different containers for each package

Fixed

  • Committees should now show up in the menu drawer.
  • Missing translations

v4.0.0

22 Aug 21:02
Compare
Choose a tag to compare

Changelog
Version 4.0.0 - 22-08-2023

This is the first release for the fully rewritten codebase of smoelenboek. There might be a few bugs here and there to iron out, but overall the rewrite allows for much more stability, performance and cleaner code.

Major Updates:

  • React Upgrade: Updated React to the latest version, ensuring we leverage the newest features and enhancements.

  • Build Tool Change: Transitioned from Create React App (RCA) to Vite for improved development speed and build performance.

  • Monorepo Transition: Updated Smoelenboek's structure to a monorepo using Yarn workspaces, streamlining package management and inter-dependency resolution.

Enhancements & Additions:

  • State Management: Integrated Redux Toolkit (RTK) for efficient and modern state management.

  • Type Safety: Ensured type safety across both the API and frontend. This guarantees consistent data structures and enhances developer experience.

  • API Improvements: Transitioned the API to utilize decorators instead of properties, simplifying codebase and increasing readability.

Replacements & Ongoing Work:

  • HTTP Client Transition: Initiated the process of replacing Axios with RTK-Query for API calls. This shift aims to benefit from RTK-Query's tight integration with Redux, caching, and automatic re-fetching capabilities. Note: This transition is currently in progress.