Skip to content

feat: async tree #7203

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
Draft
speaker-ender wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

feat: async tree #7203

speaker-ender wants to merge 5 commits into from

Conversation

@speaker-ender
Copy link
Contributor

@speaker-ender speaker-ender commented Jan 9, 2026 •
edited
Loading

Ticket []

Description Of Changes

Creating a generic async tree component + utilities to improve code maintainability and promote reuse.

TODO:

  • Improve component types
  • Add refresh functionality
  • Improve loading states
  • Move component into shared library
  • Migrate MonitorTree to utilize new component
  • Create storybook docs for new component

Code Changes

  • Adding an AsyncTree component to provide a consistent interface for handling structured async data.

Steps to Confirm

Pre-Merge Checklist

  • Issue requirements met
  • All CI pipelines succeeded
  • CHANGELOG.md updated
    • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
    • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
    • Updates unreleased work already in Changelog, no new entry necessary
  • UX feedback:
    • All UX related changes have been reviewed by a designer
    • No UX review needed
  • Followup issues:
    • Followup issues created
    • No followup issues
  • Database migrations:
    • Ensure that your downrev is up to date with the latest revision on main
    • Ensure that your downgrade() migration is correct and works
      • If a downgrade migration is not possible for this change, please call this out in the PR description!
    • No migrations
  • Documentation:
    • Documentation complete, PR opened in fidesdocs
    • Documentation issue created in fidesdocs
    • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
    • No documentation updates required

@speaker-ender
refactor: async tree
f63baa7 
wip:lots of ideas

chore: fix

wip: slowly getting there

chore: formatting

wip:lots of things

wip:so much more thinking
@speaker-ender
fix: imports
2201c3a
@speaker-ender
chore: remove maps
2d1a4ed
@speaker-ender
wip: lots of stuff done
f6b232e
@speaker-ender
wip: one foot forward two steps back
b3fa0b0
@vercel
Copy link
Contributor

vercel bot commented Jan 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
fides-plus-nightly Error Error Jan 9, 2026 4:00pm
1 Skipped Deployment
Project Deployment Review Updated (UTC)
fides-privacy-center Ignored Ignored Jan 9, 2026 4:00pm

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@speaker-ender