Skip to content

CLAUDE.md

Latest commit

 

History

History
47 lines (37 loc) · 2.27 KB

CLAUDE.md

File metadata and controls

47 lines (37 loc) · 2.27 KB

Environment Configuration Implementation Guidelines for .NET SDK

Golden Rule

When unsure about implementation details, ALWAYS ask the developer.

Implementation Status

IMPORTANT: The .NET SDK environment configuration feature is NEARLY COMPLETE and functional. Focus on bug fixes and test improvements rather than reimplementation.

Required Implementation Plans

All work on environment configuration MUST follow these plans:

  • Primary: @general-implementation-plan.md - Overall architecture and cross-SDK consistency
  • Secondary: @dotnet-implementation-plan.md - .NET-specific implementation details

Current Implementation Analysis

✅ COMPLETED Components

  1. C Bridge Layer (src/Temporalio/Bridge/sdk-core/core-c-bridge/src/envconfig.rs)

    • temporal_core_client_config_load - Loads all profiles
    • temporal_core_client_config_profile_load - Loads single profile
    • Proper memory management and error handling
    • JSON serialization between Rust and C

  2. P/Invoke Bridge (src/Temporalio/Bridge/EnvConfig.cs)

    • Complete async/await implementation
    • Proper callback handling and memory cleanup
    • JSON deserialization to .NET objects

  3. API Surface (src/Temporalio/Client/Configuration/)

    • ClientConfig - Main configuration container
    • ClientConfigProfile - Profile-specific settings
    • ClientConfigTls - TLS configuration
    • DataSource - Flexible data source abstraction
    • Integration with TemporalClientConnectOptions

Implementation Plans

All work on environment configuration MUST follow these detailed plans:

  • Primary: @general-implementation-plan.md - Overall architecture and cross-SDK consistency
  • Secondary: @dotnet-implementation-plan.md - .NET-specific implementation details and current status
  • Assessment: @envconfig-assessment.md - Comprehensive cross-SDK analysis and comparison

Current Status Summary

The .NET SDK implementation is NEARLY COMPLETE and functional, requiring only:

  1. Critical bug fix for TLS field name mismatch (see dotnet-implementation-plan.md)
  2. Comprehensive test coverage following Python/TypeScript patterns
  3. Validation of bridge layer functionality

See @dotnet-implementation-plan.md for detailed status, issues, and completion steps.