Skip to content
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

DECISION-26436_Upgrades_angular_jasmine_karma_components #171

Merged
merged 15 commits into from
Mar 23, 2022

Conversation

sundeepsapiens
Copy link
Contributor

@sundeepsapiens sundeepsapiens commented Oct 4, 2021

Upgrades_angular_jasmine_karma_components

JIRA LINK: https://jira.sapiens.com/browse/DECISION-26436

Angular: 7.3.0 -> 12.2.7
Jasmine: 3.3.0 -> 3.9.0
Karma: 3.1.1 -> 6.3.4
Typescript: 3.2.4 -> 4.3.5

@@ -58,7 +58,7 @@ export class FieldComponent {
return this.formModel && this.formModel.value;
}

private get required() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

was this causing an issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@@ -91,15 +92,15 @@ describe('FieldComponent', () => {
}));

it('should add a label style', async(() => {
expect(fixture.debugElement.query(By.css('.fx-field__label')).properties['color']).toBe(this.styleObj);
Copy link
Collaborator

Choose a reason for hiding this comment

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

if this.styleObj is not being used anymore, can you remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed newly introduced variable labelColor and updated the specs with styleObj itself

Copy link
Contributor

@urielTwito urielTwito left a comment

Choose a reason for hiding this comment

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

did you check this with our application?

});

beforeEach(async(() => fixture.detectChanges()));
beforeEach(waitForAsync(() => fixture.detectChanges()));
Copy link
Contributor

Choose a reason for hiding this comment

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

why this? waitForAsync

Copy link
Contributor Author

Choose a reason for hiding this comment

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

async has been deprecated in angular 12 (replaced with waitForAsync), initial point of time it was causing some issue of specs failure for this file and not able to run specs, so replaced with waitForAsync. But now with async, specs are running fine so reverted the changes of waitForAsync to async.

@urielTwito
Copy link
Contributor

did you check this with our application?

@sundeepsapiens
Copy link
Contributor Author

did you check this with our application?

yes, In local, I have replaced the dist folder of forms extensions with our application and changes are working fine

@urielTwito
Copy link
Contributor

LGTM

@krupasodha krupasodha merged commit b1a8785 into master Mar 23, 2022
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.

4 participants