-
Notifications
You must be signed in to change notification settings - Fork 308
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
DatePicker and DatePickerInput implementation duplicates too many classes #2822
Comments
I just found out possible 2 reasons why it might be implemented this way:
|
I agree with you on this! The structure is bloated and the change is a breaking change. I'm thinking it might make sense to make the PR target the next branch where we can release a rc version and release it officially with v12 next year. 🤔 |
Hi @Akshat55 thanks for the feedback. I agree that maybe targetting a later release is fine. For us this is not a blocking issue, just a nice improvement :) |
I noticed that the implementation for
datepicker.component.ts
anddatepicker-input.component.ts
have quite some duplication in the template.This results in the DOM with a structure like this
This is a pretty bloated DOM structure and can be simplified a lot. The react implementation is a lot simpler and has not class duplication.
I created this table as comparison, hope this works to show the problem:
.cds--form-item
>.cds--date-picker
>.cds--date-picker--container
.cds--form-item
>.cds--date-picker
.cds--form-item
>.cds--date-picker
>.cds--date-picker--container
.cds--date-picker--container
The text was updated successfully, but these errors were encountered: