-
Notifications
You must be signed in to change notification settings - Fork 1
fix: TT-262 disable buttons futures in time entries and disable input date futures #697
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
fix: TT-262 disable buttons futures in time entries and disable input date futures #697
Conversation
…-date futures in reports, test of method monthEnable
…-date futures in reports, test of method monthEnable
3d930d5
to
c9423a8
Compare
Codecov Report
@@ Coverage Diff @@
## master #697 +/- ##
==========================================
+ Coverage 93.09% 94.07% +0.98%
==========================================
Files 85 104 +19
Lines 1564 2094 +530
Branches 107 155 +48
==========================================
+ Hits 1456 1970 +514
- Misses 67 81 +14
- Partials 41 43 +2
Continue to review full report at Codecov.
|
.gitignore
Outdated
@@ -44,6 +44,7 @@ testem.log | |||
keys.ts | |||
src/environments/keys.ts | |||
debug.log | |||
/.vscode |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this part you can use *.vscode
@@ -69,4 +68,14 @@ describe('MonthPickerComponent', () => { | |||
expect(component.selectDate).toHaveBeenCalledWith(monthSelect, yearSelect); | |||
}); | |||
|
|||
it('monthEnable set disable true in the buttoms futures', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace this name:
monthEnable sets disabled to true on futures months
expect(component.monthEnable(monthFuture)).toBeTrue(); | ||
}); | ||
|
||
it('monthEnable set disable false in the buttoms presents and past', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this description is not very clear:
I Understand this.
monthEnable set disabled to false in the months presents and past
I Think is no necessary disable the past months only future months
…f github.com:ioet/time-tracker-ui into TT-262-No-select-future-dates-in-the-page-Reports
Kudos, SonarCloud Quality Gate passed!
|
This time, there is not any problem, but the objective is to disable buttons futures of component month picker, in this component added the method monthEnable. Also, disable input date futures of the dashboard of the reports, in this component added the method getCurrentDate.
Finally added two Unit testing of the method monthEnable, because this method disables buttons futures(Months futures) and enables buttons present or past(Months past/present).