Repository navigation
Add undoable graph organization - #1
Merged
Merged
Conversation
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-moss-088e7c41e-1.westus2.7.azurestaticapps.net |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Agent graphs created quickly can end up disconnected or spatially disordered even though their semantic outline already has a natural order. This makes that order actionable without forcing users to rebuild the graph manually.
Validation
npm test— 38 tests passednpm run test:e2e— 11 browser tests passednpm run build— production build passedThe repository-wide 100% coverage command still reports pre-existing uncovered lines outside this feature.