-
Notifications
You must be signed in to change notification settings - Fork 269
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
[AAE-3967] Add datetime-range search filter component #6297
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #6297 +/- ##
===========================================
+ Coverage 76.26% 78.07% +1.81%
===========================================
Files 864 353 -511
Lines 19583 9749 -9834
Branches 3901 1973 -1928
===========================================
- Hits 14935 7612 -7323
+ Misses 3475 1532 -1943
+ Partials 1173 605 -568
Continue to review full report at Codecov.
|
this.apply(this.form.value, this.form.valid); | ||
} | ||
|
||
hasValidValue() { |
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.
missing return type
return this.form.valid; | ||
} | ||
|
||
getCurrentValue() { |
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.
missing return type
moment.locale(locale); | ||
} | ||
|
||
hasParseError(formControl) { |
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.
missing return type
event.srcElement.click(); | ||
} | ||
|
||
setFromMaxDatetime(): any { |
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.
is not returning
...-services/src/lib/search/components/search-datetime-range/search-datetime-range.component.ts
Outdated
Show resolved
Hide resolved
...-services/src/lib/search/components/search-datetime-range/search-datetime-range.component.ts
Outdated
Show resolved
Hide resolved
|
||
const inputs = fixture.debugElement.nativeElement.querySelectorAll('input[ng-reflect-max="Tue Mar 10 2020 20:00:00 GMT+0"]'); | ||
|
||
expect(inputs[0]).toBeDefined(); |
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.
is toBeTruthy enough?
...ent-services/src/lib/search/components/search-date-range/search-date-range.component.spec.ts
Outdated
Show resolved
Hide resolved
it('should setup form elements on init', () => { | ||
fixture.detectChanges(); | ||
|
||
expect(component.from).toBeDefined(); |
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.
is defined in general or should it have a certain value?
--- | ||
|
||
# [Search datetime range component](../../../lib/content-services/src/lib/search/components/search-datetime-range/search-datetime-range.component.ts "Defined in search-date-range.component.ts") | ||
|
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.
shouldn't be search-datetime-range.component.ts instead of search-date-range.component.ts?
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
https://issues.alfresco.com/jira/browse/AAE-3967
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: