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

Color value component #34

Merged
merged 32 commits into from Mar 11, 2020
Merged

Color value component #34

merged 32 commits into from Mar 11, 2020

Conversation

flavens
Copy link
Collaborator

@flavens flavens commented Feb 24, 2020

closes #10

@flavens flavens added the enhancement New feature or request label Feb 24, 2020
@flavens flavens self-assigned this Feb 24, 2020
@tobiasschweizer
Copy link
Contributor

Thanks, I will review this PR today!

Copy link
Contributor

@tobiasschweizer tobiasschweizer left a comment

Choose a reason for hiding this comment

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

The picker thingy looks great. I have made some comments regarding the internal structure.

@tobiasschweizer
Copy link
Contributor

@flavens Does representing color as a string in the sub component solve your issue?

@tobiasschweizer
Copy link
Contributor

I noticed the following when running npm install:

npm WARN ngx-color-picker@9.0.0 requires a peer of @angular/common@^9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-color-picker@9.0.0 requires a peer of @angular/core@^9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-color-picker@9.0.0 requires a peer of @angular/forms@^9.0.0 but none is installed. You must install peer dependencies yourself.

Is this version made for Angular 9?

@@ -98,7 +99,7 @@ describe('ColorPickerComponent', () => {
expect(testHostComponent.form.controls.colorValue.value).toEqual('');
});

fit('should be disabled when the readonly input is set to true', () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Oh yes, that was the script searching for fit :-)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

but it has been fixed in the last commit...

Copy link
Contributor

Choose a reason for hiding this comment

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

I know :-) I was just happy that the script actually worked ;-)

Copy link
Contributor

@tobiasschweizer tobiasschweizer 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! Thanks a lot for this!

@flavens
Copy link
Collaborator Author

flavens commented Mar 11, 2020

@tobiasschweizer should I merge it now or should we wait?!?

@tobiasschweizer
Copy link
Contributor

I think it's good to go. What should we wait for?

@tobiasschweizer
Copy link
Contributor

and do not forget to hit the checkbox in #4 :-)

@flavens flavens merged commit e9cae9f into master Mar 11, 2020
@flavens flavens deleted the wip/10-color-value-component branch March 11, 2020 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Viewer Value Component: ColorValueComponent
2 participants