Date inputs update in relation to admin payment term settings #2182
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
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.
Whenever user start date input was given after the previously selected due date , the ui for calendar was broken. In this commits, I fixed this bug by setting up correct v-model updated with a new watcher and method. This watcher follows an object with unique property in date group component's instance for due date. It's because this property is being specifically updated by input change event in the responding blades.
Moreover, there is an enhancement regarding the date components. Now, the due date input is in sync with user's settings payment terms.
This changes applies to create and edit views for reconciliations, invoices and bills.
The bug:
Bug Fix and Enhancement
