Skip to content

Conversation

DavidRouyer
Copy link
Contributor

@DavidRouyer DavidRouyer commented Nov 28, 2017

  • Update dependencies
  • Remove unnecessary JSDoc tags
  • Fix build process

BREAKING CHANGE: The upgrade to Angular 5 breaks compatibility with Angular 4.

@codecov
Copy link

codecov bot commented Nov 28, 2017

Codecov Report

Merging #38 into develop will increase coverage by 0.11%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop      #38      +/-   ##
===========================================
+ Coverage    99.01%   99.13%   +0.11%     
===========================================
  Files           14       14              
  Lines          408      460      +52     
  Branches        65       79      +14     
===========================================
+ Hits           404      456      +52     
  Misses           4        4
Impacted Files Coverage Δ
src/lib/src/services/notifier.service.ts 100% <ø> (ø) ⬆️
.../src/components/notifier-notification.component.ts 100% <ø> (ø) ⬆️
...lib/src/components/notifier-container.component.ts 97.64% <ø> (+0.14%) ⬆️
src/lib/src/notifier.module.ts 100% <ø> (ø) ⬆️
src/lib/src/services/notifier-queue.service.ts 100% <ø> (ø) ⬆️
src/lib/src/models/notifier-notification.model.ts 100% <ø> (ø) ⬆️
src/lib/src/models/notifier-config.model.ts 100% <ø> (ø) ⬆️
src/lib/src/services/notifier-animation.service.ts 100% <ø> (ø) ⬆️
src/lib/src/services/notifier-timer.service.ts 100% <100%> (ø) ⬆️
... and 9 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 1b8019f...22e574a. Read the comment docs.

Copy link
Owner

@itsdevdom itsdevdom left a comment

Choose a reason for hiding this comment

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

Looks good, just have three small remarks :)

@@ -22,7 +22,7 @@ export class NotifierTimerService {
/**
* Timeout ID, used for clearing the timeout later on
*/
private timerId: number;
private timer: NodeJS.Timer;
Copy link
Owner

Choose a reason for hiding this comment

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

I think this is an issue introduced by the NodeJS typings, the timer ID here should be of type number (as before), not NodeJS.Timer. Perhaps we should cast this into a number, if necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right, TypeScript was complaining about this, I didn't check the signature of the method setTimeout which is wrong microsoft/TypeScript#842 I'll use window.setTimeout instead.

package.json Outdated
"@angular/platform-browser-dynamic": "4.1.x",
"@angular/platform-browser": "4.1.x",
"@types/jest": "20.0.x",
"@angular/common": "^5.0.3",
Copy link
Owner

@itsdevdom itsdevdom Dec 6, 2017

Choose a reason for hiding this comment

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

I usually prefer 5.0.x instead of ^5.0.3 as it is easier to understand for developers

package.json Outdated
@@ -48,64 +48,60 @@
"ci:coverage": "codecov -f coverage/coverage-final.json",
"ci:test": "jest --config tools/jest/jest.config.json --runInBand --no-cache"
},
"peerDependencies": {
Copy link
Owner

Choose a reason for hiding this comment

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

Please do not remove the peerDependencies, instead update to >= 5.0.0 < 6.0.0

@itsdevdom itsdevdom changed the title feat: Angular 5 update feat(angular): Upgrade to Angular 5 Dec 6, 2017
@DavidRouyer
Copy link
Contributor Author

@dominique-mueller I've addressed your comments :)

@itsdevdom itsdevdom merged commit 355785e into itsdevdom:develop Dec 6, 2017
@itsdevdom
Copy link
Owner

Thanks again @DavidRouyer for your contribution! I will do some further build-related updates and release v3 of angular-notifier in the next few days.

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.

2 participants