Chore: update main from develop

[JustSamuel]

Description

Related issues/external references

Style reworks, updated README and other fixes.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

[github-actions]

Triggered from #433 by @​JustSamuel.

Checking if we can fast forward main (e5bb95a) to develop (e74fc57).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit e74fc5713ca2ba165bf7e62310e811edcd4ea3f8 (pull_request/develop)
Author: Ruben Lagerwerf <[email protected]>
Date:   Tue Oct 29 22:48:56 2024 +0100

    feat(dashboard): Add maintenance screen (#422)

It is possible to fast forward main (e5bb95a) to develop (e74fc57). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.

[github-actions]

Triggered from #433 by @​SuperVK.

Checking if we can fast forward main (e5bb95a) to develop (026a5ed).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit 026a5ed700cf9c9126057ca0ecb132a887db7186 (pull_request/develop)
Author: Tom Udding <[email protected]>
Date:   Thu Oct 31 19:24:51 2024 +0100

    fix(dashboard/user-topup-modal): prevent clicking payment button multiple times (#436)
    
    Pressing the "PAY" button starts the confirmation of the Payment Intent of the
    current top-up. This sends a request to Stripe which will (if successful) return
    a payment redirect link for iDEAL transactions.
    
    Unfortunately, due to various reasons it is possible to accidentally press the
    "PAY" button twice. This can be due to user error, device issues, or network
    issues. The result is that sometimes, the request to confirm the Payment Intent
    is send twice. This means that two payment redirect links are generated by
    Stripe, but only the first one will be used.
    
    Because Stripe has generated the second link (or even more) only that link is
    still active for Stripe. In other words, successful payments through the first
    link are not actively confirmed by Stripe. This means that that money is
    "temporarily" considered lost and the top-up is not successful.
    
    The money will be returned to the user by Stripe within 5 business days,
    however, we should do everything in our power to ensure that this does not
    happen (especially because people sometimes need to do large top-ups).
    
    This change ensures that the "PAY" button is disabled after pressing it until
    the user is redirected to the iDEAL payment page. I would have loved to use an
    `Idempotency-Key` instead, however, it appears that this is not directly
    supported by the `confirmPayment` method.

It is possible to fast forward main (e5bb95a) to develop (026a5ed). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.

[github-actions]

Triggered from #433 by @​SuperVK.

Checking if we can fast forward main (e5bb95a) to develop (201fae0).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit 201fae0ecd8c6f2b79af862e11f9c81a7b56001f (pull_request/develop)
Author: Victor Klomp <[email protected]>
Date:   Thu Oct 31 20:01:49 2024 +0100

    feat(fine): Ability to partially waive fines (#429)
    
    * feat(fines): Partially waive fines
    
    * fix(fines): Make mutation refresh after partially waiving fine
    
    * fix(fines): Form validation for waiving above the possible amount of fines
    
    * fix(fines): Fix issues from Samuel
    
    * fix(fines): Add info text for waiving fines
    
    * fix(fines): Add button to waive all fines.
    
    * fix(fines): Typo
    
    * fix(fines): Let the last fine waive be the placeholder
    
    * fix(fines): Don't render waive fines when no fine
    
    * fix(fines): Typing issues

It is possible to fast forward main (e5bb95a) to develop (201fae0). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.

[SuperVK]

Fine by me to merge, but this will mean that the POS styling is now actuality (which is fine by me)

[JustSamuel]

Fine by me to merge, but this will mean that the POS styling is now actuality (which is fine by me)

Yeah I'll change the background later, since that seems to be the "issue"

[github-actions]

Triggered from #433 by @​noelvandevrie.

Checking if we can fast forward main (e5bb95a) to develop (dd10e7b).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit dd10e7b0c5b3033d2a4d60f6651012f662c96dfc (pull_request/develop)
Author: Noel van de Vrie <[email protected]>
Date:   Fri Nov 1 17:41:57 2024 +0100

    Feature/nfc update (#437)
    
    * feat(dashboard/profile) Initial addition of NFC form
    
    * fix: added locales
    
    added additional locales where they were still missing and improved naming of them.
    
    * feat(dashboard/profile)
    
    Changed where the scanner is opened and removed the dialog and form scanner should now work on mobile chrome browsers
    
    * fix(dashboard/nfc-reader): Addresses remarks in pull request
    
    Addresses remarks made in the pull request by @justSamuel
    
    * fix(dashboard/profile):
    
    removed console.log and whitespace

It is possible to fast forward main (e5bb95a) to develop (dd10e7b). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.

[github-actions]

Triggered from #433 by @​JustSamuel.

Checking if we can fast forward main (e5bb95a) to develop (a61cdec).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit a61cdec8457a34d284334767514ee3952d783b25 (pull_request/develop)
Author: Samuel <[email protected]>
Date:   Sat Nov 2 13:18:12 2024 +0100

    fix: remove topup warning on landing page (#438)

It is possible to fast forward main (e5bb95a) to develop (a61cdec). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.

[github-actions]

Triggered from #433 by @​JustSamuel.

Checking if we can fast forward main (e5bb95a) to develop (799b1c8).

Target branch (main):

commit e5bb95a6b322a3b3a862d99c0ea67489269859ee (HEAD -> main, tag: v1.8.1, origin/main)
Author: Ruben Lagerwerf <[email protected]>
Date:   Sun Oct 13 14:04:37 2024 +0200

    fix: flagged transaction email is cut off (#365)

Pull request (develop):

commit 799b1c8d92c7dbaa69ec5935f0f1929a4c5c9ae6 (pull_request/develop)
Author: Samuel <[email protected]>
Date:   Sat Nov 2 13:51:33 2024 +0100

    feat: post refactoring invoice ui (#335)

It is possible to fast forward main (e5bb95a) to develop (799b1c8). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to develop.