Skip to content

Conversation

gqroot
Copy link

@gqroot gqroot commented Nov 26, 2020

image

@gqroot gqroot linked an issue Nov 26, 2020 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Nov 26, 2020

Codecov Report

Merging #580 (329ab0a) into master (13de42e) will increase coverage by 0.27%.
The diff coverage is 94.73%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #580      +/-   ##
==========================================
+ Coverage   93.09%   93.36%   +0.27%     
==========================================
  Files          85       92       +7     
  Lines        1564     1613      +49     
  Branches      107      105       -2     
==========================================
+ Hits         1456     1506      +50     
- Misses         67       69       +2     
+ Partials       41       38       -3     
Impacted Files Coverage Δ
src/app/app-routing.module.ts 100.00% <ø> (ø)
...les/shared/components/sidebar/sidebar.component.ts 88.88% <ø> (ø)
...dules/time-entries/pages/time-entries.component.ts 82.81% <ø> (ø)
src/app/modules/users/store/user.reducers.ts 62.50% <62.50%> (ø)
...ponents/details-fields/details-fields.component.ts 92.20% <100.00%> (+5.02%) ⬆️
...sers/components/users-list/users-list.component.ts 100.00% <100.00%> (ø)
src/app/modules/users/pages/users.component.ts 100.00% <100.00%> (ø)
src/app/modules/users/services/users.service.ts 100.00% <100.00%> (ø)
src/app/modules/users/store/user.actions.ts 100.00% <100.00%> (ø)
src/app/modules/users/store/user.effects.ts 100.00% <100.00%> (ø)
... and 8 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c1aa529...329ab0a. Read the comment docs.

@gqroot gqroot force-pushed the 566_ManualTimeEntries branch from eab4210 to 22a3250 Compare November 26, 2020 23:02
@gqroot gqroot force-pushed the 566_ManualTimeEntries branch from 22a3250 to 4aa0c14 Compare November 26, 2020 23:16
@@ -311,7 +315,7 @@ describe('DetailsFieldsComponent', () => {
spyOn(toastrServiceStub, 'error');

const futureDate = moment().add(1, 'days').format('YYYY-MM-DD');
component.entryForm.setValue({ ...formValues, entry_date: futureDate });
component.entryForm.setValue({ ...formValues, entry_date: futureDate, departure_date: futureDate });
component.onSubmit();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add a couple of tests here:

  1. start_date in the future / end date OK
  2. start_date OK / end date in the future

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@enriquezrene
Copy link
Contributor

It seems much more user friendly to show in the same row the start date/time, and in the next row the end date/time. This may lead to confusion.

image

@gqroot gqroot changed the title feat: #566 Datepicker for Date out feat: #566 Datepicker for departure date in entry form Nov 27, 2020
@gqroot gqroot merged commit 2eef09e into master Nov 30, 2020
@gqroot gqroot deleted the 566_ManualTimeEntries branch November 30, 2020 22:53
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.

Allow time-entries creation in more than one day
3 participants