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

Tree #2882

Open
5 tasks
joshwooding opened this issue Jan 5, 2024 · 12 comments
Open
5 tasks

Tree #2882

joshwooding opened this issue Jan 5, 2024 · 12 comments

Comments

@joshwooding
Copy link
Contributor

joshwooding commented Jan 5, 2024

Tasks

  1. 0 of 10
    component: tree role: content 📝 role: design 🎨 role: dev 💻 type: enhancement 💡
  2. 0 of 10
    component: tree role: content 📝 role: design 🎨 role: dev 💻 type: enhancement 💡
  3. 0 of 10
    component: tree role: content 📝 role: design 🎨 role: dev 💻 type: enhancement 💡
  4. 0 of 10
    component: tree role: content 📝 role: design 🎨 role: dev 💻 type: enhancement 💡
  5. 0 of 10
    component: tree role: content 📝 role: design 🎨 role: dev 💻 type: enhancement 💡
@navkaur76
Copy link
Contributor

navkaur76 commented Feb 7, 2024

Kick off meeting notes (w/ Darrin, Josh, Mike + Nav):

Variants to focus on for this sprint:

  • Default/single-select
  • Checkbox support + relevant multi-select behaviour. Would be nice to include shift key behaviour for selecting/highlighting multiple tree items
  • Icon support

Styling updates this sprint:

  • Will use chevrons, not triangle/caret icon
  • Tree updated with List styling

Park for future sprint:

  • All asynchronous states
  • Error state
  • Drag and drop functionality + styling

Core partners: MTK (Richard S.) + Fusion (Oykun)

@joshwooding joshwooding changed the title Tree Tree Component Development Feb 27, 2024
@mark-tate mark-tate changed the title Tree Component Development Tree Apr 9, 2024
@mark-tate mark-tate reopened this Apr 10, 2024
@origami-z
Copy link
Contributor

Modify dates, shifting order with other components

@mark-tate
Copy link
Contributor

Moving to Q3, design available but requires spec review

@mark-tate
Copy link
Contributor

expected to be 4 sprints - 1 sprint design, 3 sprint build

@mark-tate
Copy link
Contributor

Galao Goal: a11y review of tree

@origami-z
Copy link
Contributor

Searched SourceGraph, excluding UITK repo, 477 usage <Tree

@mark-tate
Copy link
Contributor

mark-tate commented Oct 14, 2024

Latte Goal: kickoff to define the requirements of Tree

@jake-costa
Copy link

Current Figma Specs for tree have been reviewed, comments have been added. Connecting with @ivan-calderon tomorrow to review and finalize.

Still needed: a kickoff to define the requirements of Tree (Lungo Goal?)

@dplsek
Copy link

dplsek commented Oct 25, 2024

@jake-costa adding a11y comments to the existing spec, no new design work has been started. requirements need to be established for this.

@mark-tate
Copy link
Contributor

Lungo Goal: Design to review a11y feedback and understand any work required
Kickoff requirements after design review
@ivan-calderon to create kickoff

@mark-tate
Copy link
Contributor

Macc Goal: No work in this sprint

Design capacity in Mocha
Dev review in Mocha
Tree build is at-risk of moving to Q1 due to capacity

@origami-z
Copy link
Contributor

Rest of Q4 - Gather requirements, development won't start until 1Q25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

6 participants