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

Need expand/collapse events for Tree #8945

Open
1 of 6 tasks
avkolomeets opened this issue Mar 15, 2024 · 1 comment
Open
1 of 6 tasks

Need expand/collapse events for Tree #8945

avkolomeets opened this issue Mar 15, 2024 · 1 comment
Labels
0 - new New issues that need assignment. ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. ArcGIS GeoBIM Issues logged by ArcGIS GeoBIM team members. blocked This issue is blocked by another issue. c-tree Issues that pertain to the calcite-tree and related components enhancement Issues tied to a new feature or request. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p3 - want for upcoming milestone User set priority status of p3 - want for upcoming milestone

Comments

@avkolomeets
Copy link

avkolomeets commented Mar 15, 2024

Check existing issues

Description

Need events to track expanding/collapsing of items.

Acceptance Criteria

Need events like calciteTreeExpand / calciteTreeCollapse.

Relevant Info

No response

Which Component

Tree

Example Use Case

We have a tree with top level items representing projects. Loading attributes for each project takes time, so we don't load all at once. When a user clicks to expand a project, we show a loading and then update the tree to show attributes. Can't detect a moment when a node was expanded, because events are not emitted.

Priority impact

p3 - want for upcoming milestone

Calcite package

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

Esri team

ArcGIS Business/Community Analyst

@avkolomeets avkolomeets added 0 - new New issues that need assignment. enhancement Issues tied to a new feature or request. needs triage Planning workflow - pending design/dev review. labels Mar 15, 2024
@github-actions github-actions bot added p3 - want for upcoming milestone ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. labels Mar 15, 2024
@ialixandroae
Copy link

Thank you for having this issue created! At ArcGIS GeoBIM we would need the same events.

@geospatialem geospatialem added the ArcGIS GeoBIM Issues logged by ArcGIS GeoBIM team members. label Apr 22, 2024
@geospatialem geospatialem added impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone and removed p3 - want for upcoming milestone labels May 21, 2024
@geospatialem geospatialem added c-tree Issues that pertain to the calcite-tree and related components blocked This issue is blocked by another issue. labels Aug 27, 2024
@github-actions github-actions bot added the p3 - want for upcoming milestone User set priority status of p3 - want for upcoming milestone label Aug 27, 2024
@geospatialem geospatialem removed the needs triage Planning workflow - pending design/dev review. label Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. ArcGIS GeoBIM Issues logged by ArcGIS GeoBIM team members. blocked This issue is blocked by another issue. c-tree Issues that pertain to the calcite-tree and related components enhancement Issues tied to a new feature or request. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p3 - want for upcoming milestone User set priority status of p3 - want for upcoming milestone
Projects
None yet
Development

No branches or pull requests

3 participants