-
Notifications
You must be signed in to change notification settings - Fork 2
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frontend Run #2156
Run Properties:
|
Project |
frontend
|
Branch Review |
feat/available-from-default-next-month
|
Run status |
Passed #2156
|
Run duration | 01m 40s |
Commit |
280c851f13 ℹ️: Merge 70600ddee2ba99774ca8463419727537dea08609 into 65f6c8d188d6676daa7957b107ad...
|
Committer | morre |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
0
|
Skipped |
0
|
Passing |
32
|
View all changes introduced in this branch ↗︎ |
morremeyer
force-pushed
the
feat/available-from-default-next-month
branch
from
November 23, 2024 18:41
a78c3e4
to
1e7a2c6
Compare
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
force-pushed
the
feat/available-from-default-next-month
branch
from
November 23, 2024 20:08
1e7a2c6
to
b101789
Compare
malfynnction
approved these changes
Nov 23, 2024
frontend Run #2166
Run Properties:
|
Project |
frontend
|
Branch Review |
main
|
Run status |
Passed #2166
|
Run duration | 01m 40s |
Commit |
52df7a4b50: fixup! feat!: set default available from to next month
|
Committer | Morre |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
0
|
Skipped |
0
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.