Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat!: set default available from to next month #1775

Merged
merged 2 commits into from
Nov 23, 2024

Conversation

morremeyer
Copy link
Member

With this, the default AvailableFrom date is set to the first of the month following the transaction, not the month of the transaction.

This makes more sense logically since it enforces funds to only be allocated after they have been received by default.
The value can still be explicitly set if that is required.

@morremeyer morremeyer requested a review from a team as a code owner November 23, 2024 18:21
Copy link

cypress bot commented Nov 23, 2024

frontend    Run #2156

Run Properties:  status check passed Passed #2156  •  git commit 280c851f13 ℹ️: Merge 70600ddee2ba99774ca8463419727537dea08609 into 65f6c8d188d6676daa7957b107ad...
Project frontend
Branch Review feat/available-from-default-next-month
Run status status check passed Passed #2156
Run duration 01m 40s
Commit git commit 280c851f13 ℹ️: Merge 70600ddee2ba99774ca8463419727537dea08609 into 65f6c8d188d6676daa7957b107ad...
Committer morre
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 32
View all changes introduced in this branch ↗︎

@morremeyer morremeyer force-pushed the feat/available-from-default-next-month branch from a78c3e4 to 1e7a2c6 Compare November 23, 2024 18:41
With this, the default AvailableFrom date is set to the first of the month following the transaction, not the month of the transaction.

This makes more sense logically since it enforces funds to only be allocated after they have been received by default.
The value can still be explicitly set if that is required.

The onChange function now just keeps the existing value and does not try to set it to the first of the next month, since that would set a future date every time the field is edited.
@morremeyer morremeyer force-pushed the feat/available-from-default-next-month branch from 1e7a2c6 to b101789 Compare November 23, 2024 20:08
@morremeyer morremeyer added this pull request to the merge queue Nov 23, 2024
Merged via the queue into main with commit 52df7a4 Nov 23, 2024
13 checks passed
@morremeyer morremeyer deleted the feat/available-from-default-next-month branch November 23, 2024 21:38
Copy link

cypress bot commented Nov 23, 2024

frontend    Run #2166

Run Properties:  status check passed Passed #2166  •  git commit 52df7a4b50: fixup! feat!: set default available from to next month
Project frontend
Branch Review main
Run status status check passed Passed #2166
Run duration 01m 40s
Commit git commit 52df7a4b50: fixup! feat!: set default available from to next month
Committer Morre
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 32
View all changes introduced in this branch ↗︎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants