Terminal.Gui/PR_DESCRIPTION_UPDATED.md

Fixes #4329 - Major Architectural Improvements: API Rename, Nullable Types, and Application Decoupling

Overview

This PR delivers three major architectural improvements to Terminal.Gui v2:

1. API Terminology Modernization - Renamed confusing Application.Top/TopLevels to intuitive Application.Current/Session Stack
2. Nullable Reference Types - Enabled nullable for 143 non-View library files
3. Application Decoupling - Introduced View.App property to decouple View hierarchy from static Application class

Impact: 561 files changed, 7,033 insertions(+), 2,736 deletions(-) across library, tests, and examples.

---

Part 1: API Terminology Modernization (Breaking Change)

Changes

• Application.Top → Application.Current (684 occurrences across codebase)
• Application.TopLevels → Application.SessionStack (31 occurrences)
• Updated IApplication interface, ApplicationImpl, all tests, examples, and documentation

Rationale

The old naming was ambiguous and inconsistent with .NET patterns:

• Top didn't clearly indicate "currently active/running view"
• TopLevels exposed implementation detail (it's a stack!) and didn't match SessionToken terminology

New naming follows established patterns:

• Current matches Thread.CurrentThread, HttpContext.Current, Synchronization Context.Current
• SessionStack clearly describes both content (sessions) and structure (stack), aligning with SessionToken

Impact Statistics

Category	Files Changed	Occurrences Updated
Terminal.Gui library	41	715
Unit tests	43	631
Integration tests	3	25
Examples	15	15
Documentation	3	14
Total	91	~800

###Breaking Changes

All references must be updated:

// OLD (v1/early v2)
Application.Top?.SetNeedsDraw();
foreach (var tl in Application.TopLevels) { }

// NEW (v2 current)
Application.Current?.SetNeedsDraw();
foreach (var tl in Application.SessionStack) { }

---

Part 2: Nullable Reference Types Enabled

Changes

Phase 1 - Project Configuration (commit 439e161):

• Added <Nullable>enable</Nullable> to Terminal.Gui.csproj (project-wide default)
• Removed redundant #nullable enable from 37 files
• Added #nullable disable to 170 files not yet compliant

Phase 2 - Non-View Compliance (commit 06bd50d):

• Removed #nullable disable from ALL 143 non-View library files
• Build successful with 0 errors
• All core infrastructure now fully nullable-aware

Phase 3 - Cleanup (commits 97d9c7d, 49d4fb2):

• Fixed duplicate #nullable directives in 37 files
• All files now have clean, single nullable directive

Impact Statistics

Directory	Files Nullable-Enabled
App/	25 ✅
Configuration/	24 ✅
ViewBase/	30 ✅
Drivers/	25 ✅
Drawing/	18 ✅
FileServices/	7 ✅
Input/	6 ✅
Text/	5 ✅
Resources/	3 ✅
Views/	121 ⏸️ (documented in NULLABLE_VIEWS_REMAINING.md)
Total Enabled	143 files

Remaining Work

See NULLABLE_VIEWS_REMAINING.md for the 121 View subclass files still with #nullable disable. These require careful migration due to complex view hierarchies and will be addressed in a follow-up PR.

---

Part 3: Application Decoupling (MASSIVE Change)

Problem

Prior to this PR, Views were tightly coupled to the static Application class:

• Direct static calls: Application.Current, Application.Driver, Application.MainLoop
• Made Views untestable in isolation
• Violated dependency inversion principle
• Prevented Views from working with different IApplication implementations

Solution: View.App Property

Introduced View.App property that provides IApplication instance:

// Terminal.Gui/ViewBase/View.cs
public IApplication? App
{
    get => GetApp();
    internal set => _app = value;
}

private IApplication? GetApp()
{
    // Walk up hierarchy to find IApplication
    if (_app is { }) return _app;
    if (SuperView is { }) return SuperView.App;
    return Application.Instance;  // Fallback to global
}

Migration Pattern

Before (tightly coupled):

// Direct static dependency
Application.Driver.Move(x, y);
if (Application.Current == this) { }
Application.MainLoop.Invoke(() => { });

After (decoupled via View.App):

// Use injected IApplication instance
App?.Driver.Move(x, y);
if (App?.Current == this) { }
App?.MainLoop.Invoke(() => { });

Impact Statistics

• 90 files changed in decoupling commit (899fd76)
• 987 insertions, 728 deletions
• Affects ViewBase, Views, Adornments, Input handling, Drawing

Benefits

✅ Testability: Views can now be tested with mock IApplication
✅ Flexibility: Views work with any IApplication implementation
✅ Cleaner Architecture: Follows dependency injection pattern
✅ Future-proof: Enables multi-application scenarios
✅ Maintainability: Clearer dependencies, easier to refactor

Known Remaining Coupling

After decoupling work, only 1 direct Application dependency remains in ViewBase:

• Border.Arrangement.cs: Uses Application.ArrangeKey for hotkey binding

Additional investigation areas for future work:

1. Some Views still reference Application for convenience (non-critical)
2. Test infrastructure may have residual static dependencies
3. Example applications use Application.Run (expected pattern)

---

Part 4: Test Infrastructure Improvements

New Test File: ApplicationImplBeginEndTests.cs

Added 16 comprehensive tests validating fragile Begin/End state management:

Critical Test Coverage:

• End_ThrowsArgumentException_WhenNotBalanced - Ensures proper Begin/End pairing
• End_RestoresCurrentToPreviousToplevel - Validates Current property management
• MultipleBeginEnd_MaintainsStackIntegrity - Tests nested sessions (5 levels deep)

Additional Coverage:

• Argument validation (null checks)
• SessionStack push/pop operations
• Current property state transitions
• Unique ID generation for toplevels
• SessionToken management
• ResetState cleanup behavior
• Toplevel activation/deactivation events

Test Quality Improvements

All new tests follow best practices:

• Work directly with ApplicationImpl instances (no global Application pollution)
• Use try-finally blocks ensuring Shutdown() always called
• Properly dispose toplevels before Shutdown (satisfies DEBUG_IDISPOSABLE assertions)
• No redundant ResetState calls (Shutdown calls it internally)

Result: All 16 new tests + all existing tests passing ✅

---

Additional Changes

Merged from v2_develop

• RunState → SessionToken terminology (precedent for this rename)
• Application.TopLevels visibility changed to public (made this rename more important)
• Legacy MainLoop infrastructure removed
• Driver architecture modernization
• Test infrastructure improvements

Documentation

• Created 5 comprehensive terminology proposal documents in docfx/docs/:
  • terminology-index.md - Navigation guide
  • terminology-proposal.md - Complete analysis
  • terminology-proposal-summary.md - Quick reference
  • terminology-diagrams.md - 11 Mermaid diagrams
  • terminology-before-after.md - Side-by-side examples
• Updated navigation.md, config.md, migratingfromv1.md
• Created NULLABLE_VIEWS_REMAINING.md - Tracks remaining nullable work

---

Testing

• ✅ Build: Successful with 0 errors
• ✅ Unit Tests: All 16 new tests + all existing tests passing
• ✅ Integration Tests: Updated and passing
• ✅ Examples: UICatalog, ReactiveExample, CommunityToolkitExample all updated and functional
• ✅ Documentation: Builds successfully

---

Breaking Changes Summary

API Changes (Requires Code Updates)

1. Application.Top → Application.Current

   • All usages must be updated
   • Affects any code accessing the currently running toplevel

2. Application.TopLevels → Application.SessionStack

   • All usages must be updated
   • Affects code iterating over running sessions

Non-Breaking Changes

• Nullable reference types: Improved type safety, no runtime changes
• View.App property: Additive, existing Application. * calls still work (for now)

---

Migration Guide

For Terminology Changes

# Find and replace in your codebase
Application.Top → Application.Current
Application.TopLevels → Application.SessionStack

For View.App Usage (Recommended, Not Required)

When writing new View code or refactoring existing Views:

// Prefer (future-proof, testable)
App?.Driver.AddRune(rune);
if (App?.Current == this) { }

// Over (works but tightly coupled)
Application.Driver.AddRune(rune);
if (Application.Current == this) { }

---

Future Work

Nullable Types

• Enable nullable for remaining 121 View files
• Document nullable patterns for View subclass authors

Application Decoupling

• Remove last Application.ArrangeKey reference from Border
• Consider making View.App property public for advanced scenarios
• Add documentation on using View.App for testable Views

Tests

• Expand ApplicationImpl test coverage based on new patterns discovered
• Add tests for View.App hierarchy traversal

---

Pull Request Checklist

• I've named my PR in the form of "Fixes #issue. Terse description."
• My code follows the style guidelines of Terminal.Gui
• My code follows the Terminal.Gui library design guidelines
• I ran dotnet test before commit
• I have made corresponding changes to the API documentation
• My changes generate no new warnings
• I have checked my code and corrected any poor grammar or misspellings
• I conducted basic QA to assure all features are working

---

Related Issues

• Fixes #4329 - Rename/Clarify Application.Toplevels/Top Terminology
• Related to #2491 - Toplevel refactoring
• Fixes #4333 (duplicate/related issue)

---

Note: This is a large, multi-faceted PR that delivers significant architectural improvements. The changes are well-tested and maintain backward compatibility except for the intentional breaking API rename. The work positions Terminal.Gui v2 for better testability, maintainability, and future enhancements.