-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(select): ghost select #1133
Conversation
🚀 Latest successful build of the PR deployed here. 🚀 |
@@ -48,6 +48,9 @@ export class VWCSelect extends MWCSelect { | |||
@property({ type: String, reflect: true }) | |||
name: string | undefined; | |||
|
|||
@property({ type: Boolean, reflect: true, attribute: 'ghost' }) |
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.
This needs to be tested.
Also, need to test the logic that's bound to it:
If ghost is true, dense must be true (at least that's what I see in the code).
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.
should we enforce programmatically? it's that mutating user's definition discussion again...
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.
We need because of the design. As I wrote in the summery of this PR its a quick & dirty fix. This component is different from our conventions in a lot of ways...
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.
LGTM
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Quick and dirty adding a ghost layout.
Unable to use our layout because there's already a Layout function in MVC.
Ghost select only goes with dense. As Joella asked.