Skip to content

style(drop-down): Adding classes for different density types #5036

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

Merged
merged 21 commits into from
Jun 20, 2019

Conversation

desig9stein
Copy link
Contributor

@desig9stein desig9stein commented Jun 10, 2019

Closes #2960

Additional information (check all that apply):

  • Bug fix
  • New functionality
  • Documentation
  • Demos
  • CI/CD

Checklist:

  • All relevant tags have been applied to this PR
  • This PR includes unit tests covering all the new code
  • This PR includes API docs for newly added methods/properties
  • This PR includes feature/README.MD updates for the feature docs
  • This PR includes general feature table updates in the root README.MD
  • This PR includes CHANGELOG.MD updates for newly added functionality
  • This PR contains breaking changes
  • This PR includes ng update migrations for the breaking changes
  • This PR includes behavioral changes and the feature specification has been updated with them

@PlamenaMiteva PlamenaMiteva added 💥 status: in-test PRs currently being tested and removed ❌ status: awaiting-test PRs awaiting manual verification labels Jun 18, 2019
@PlamenaMiteva PlamenaMiteva added ✅ status: verified Applies to PRs that have passed manual verification and removed 💥 status: in-test PRs currently being tested labels Jun 18, 2019
@wnvko wnvko changed the title style(drop-down): Aadding classes for different density types style(drop-down): Adding classes for different density types Jun 18, 2019
Copy link
Contributor

@wnvko wnvko left a comment

Choose a reason for hiding this comment

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

Update and the check list and do not forget to update the specification.

@@ -196,6 +212,22 @@ export abstract class IgxDropDownItemBase implements DoCheck {
@HostBinding('class.igx-drop-down__header')
public isHeader: boolean;

/**
Copy link
Contributor

Choose a reason for hiding this comment

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

drop down could update its items display density via hidden input. This way items will not know about drop down. Other possible solution is to use some service to update display density of the items.

Copy link
Contributor

Choose a reason for hiding this comment

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

I believe this would be better left for another PR - in order for the drop-down item to not know about it's parent, the remaining selection logic and the allowItemFocus handling inside of the drop-down-item component will have to be abstracted in a service as well

…pec, #5034

# Conflicts:
#	projects/igniteui-angular/src/lib/drop-down/drop-down.component.spec.ts
…on strat;

# Conflicts:
#	projects/igniteui-angular/src/lib/drop-down/drop-down.common.ts
@wnvko wnvko self-requested a review June 19, 2019 11:29
@Lipata Lipata merged commit 2d082e4 into 7.2.x Jun 20, 2019
@ChronosSF ChronosSF deleted the add-density-to-drop-down_7.2.x branch December 3, 2019 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants