-
Notifications
You must be signed in to change notification settings - Fork 11
chore: update angular #399
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -38,11 +38,11 @@ export class ColorService { | |
| } | ||
|
|
||
| public brighter(colorHex: string, basis: number): string { | ||
| return rgb(colorHex).brighter(basis).hex(); | ||
| return rgb(colorHex).brighter(basis).formatHex(); | ||
| } | ||
|
|
||
| public darker(colorHex: string, basis: number): string { | ||
| return rgb(colorHex).darker(basis).hex(); | ||
| return rgb(colorHex).darker(basis).formatHex(); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why this change? I dont see d3 being updated with this pr.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was a deprecation called out by the linter. If I were to guess, we got a new locked version of d3-color that was still compatible with the version spec in package.json |
||
| } | ||
|
|
||
| private getBasisColors(key: ColorPaletteKey): string[] { | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,10 @@ | ||
| import { fakeAsync } from '@angular/core/testing'; | ||
| import { MAT_SNACK_BAR_DATA } from '@angular/material/snack-bar'; | ||
| import { IconType } from '@hypertrace/assets-library'; | ||
| import { IconComponent } from '@hypertrace/components'; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does the new compiler catches these circular dependencies in test?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nope - I manually fixed all these because of the ngcc issue above. I thought the circular references breaking ngcc were our own, but it ended up being spectator. Since I had already fixed them, I left them in. |
||
| import { createHostFactory, SpectatorHost } from '@ngneat/spectator/jest'; | ||
| import { MockComponent } from 'ng-mocks'; | ||
| import { Subject } from 'rxjs'; | ||
| import { IconComponent } from '../icon/icon.component'; | ||
| import { NotificationComponent, NotificationMode } from './notification.component'; | ||
|
|
||
| describe('NotificationComponent', () => { | ||
|
|
||
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.
What does these new options do?
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.
so previously, we were running ngcc across all test dependencies. The issue there is that spectator and spectator jest circularly reference each other (not sure why this wasn't an issue in the past) and break. We don't actually need spectator to be compiled for ivy though - so now we're using
--tsconfig './tsconfig.app.json' --use-program-dependenciesto only compile modules reference from the actual application, and then manually addingngcc --source 'node_modules/@angular'to compile the angular testing modules used by the test bed (and we know all the first party angular ones are compatible with the ivy compiler anyway).