You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ac8a858
Browse filesBrowse the repository at this point in the historyBrowse files
feat(edge-worker): add workerConfig to handler execution context (#203)
Adds workerConfig to handler execution context, allowing handlers to access worker configuration for intelligent decision-making based on retry limits, concurrency settings, and other parameters.
Key Changes
Added workerConfig to MessageExecution and StepTaskExecution contexts
Deep frozen config prevents accidental handler modifications while keeping worker config mutable
Performance optimized - config frozen once at startup and cached for reuse
Reorganized configuration handling with cleaner factory methods and consolidated defaults
Simplified EdgeWorker API by removing unnecessary union types
Environment variables always sourced from platform (users cannot override)
Handlers can now access worker configuration through `context.workerConfig` to make intelligent decisions based on retry limits, concurrency settings, and other worker parameters. The config is deeply frozen to prevent accidental modifications while remaining mutable by the worker itself for future features.
8
+
9
+
Key improvements:
10
+
- Added `workerConfig` to MessageExecution and StepTaskExecution contexts
11
+
- Config is cached and frozen once at startup for optimal performance
12
+
- Reorganized configuration handling with cleaner factory methods
13
+
- Simplified EdgeWorker API by removing unnecessary union types
14
+
- Environment variables always sourced from platform (users cannot override)
0 commit comments