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.

Sign up for GitHub

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

Jump to bottom

[Tree Item] Add "item selection" event #10978

Open
2 of 5 tasks
macandcheese opened this issue Dec 4, 2024 · 0 comments
Open
2 of 5 tasks

[Tree Item] Add "item selection" event #10978

macandcheese opened this issue Dec 4, 2024 · 0 comments
Labels
0 - new New issues that need assignment. c-tree Issues that pertain to the calcite-tree and related components Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - medium Issue is non core or affecting less that 60% of people using the library

Comments

@macandcheese
Copy link
Contributor

Check existing issues

Description

To better match our current patterns, it would be nice if each Tree Item emits its own selection event. Currently, there is only a parent-level event emitted.

Acceptance Criteria

A treeItemSelect event or similar is added to align with patterns from other parent / child components supporting selection.

Relevant Info

Related Tree Event issues:
#6950
#8945

Community post:
https://community.esri.com/t5/calcite-design-system-questions/calcitetree-react/m-p/1561776#M780

Which Component

Tree / Tree Item

Example Use Case

As a developer, I want to listen for the event emitted on an individual Tree Item.

Priority impact

impact - p2 - want for an upcoming milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (design)
@macandcheese macandcheese added enhancement Issues tied to a new feature or request. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Dec 4, 2024
@github-actions github-actions bot added Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone labels Dec 4, 2024
@macandcheese macandcheese added the c-tree Issues that pertain to the calcite-tree and related components label Dec 24, 2024
@driskull driskull added p - medium Issue is non core or affecting less that 60% of people using the library estimate - 3 A day or two of work, likely requires updates to tests. labels Feb 25, 2025
@DitwanP DitwanP added needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. labels Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. c-tree Issues that pertain to the calcite-tree and related components Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - medium Issue is non core or affecting less that 60% of people using the library
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@driskull @macandcheese @DitwanP