Repository navigation
Add embedded Code to desktop footer navigation - #10
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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.
Adds Code beside Terminal in the desktop footer when a compatible local editor runtime is available. Existing Chat and application navigation retain their current implementation; switching destinations keeps editor files open in the same native window.
The optional adapter confines activation to the application main frame on loopback, keeps the editor connection URL out of renderer state, preserves the Dpro header/footer, and stops its owned runtime during shutdown. The internal editor implementation is maintained separately and is not included in this public change. Production runtime packaging and installer updates remain separate release work.
Validation: 45 desktop tests, 27 focused UI/application tests, strict TypeScript checking of 242 UI sources, and local native acceptance covering file save, draft preservation, footer-only Code navigation, Terminal navigation and clean shutdown. Eight native light/dark layout cases passed within the host display limits. No credentials, local account fixtures, generated builds, profiles or internal planning documents are included.
Manifest validation uses one opened handle for its bounded read, and preview settings are created exclusively so a competing file or symbolic link cannot be overwritten. Both filesystem regressions are covered.