feat: expose application properties via Options for TypeScriptBootstrapModifier consumers (#24073) (CP: 25.0)#24252
Conversation
…strapModifier` consumers (#24073) `TypeScriptBootstrapModifier` implementations (e.g., Copilot) need access to application properties to conditionally modify bootstrap TypeScript. Currently, the Copilot script is injected in dev mode regardless of whether Copilot is enabled in the project configuration. Add `withApplicationConfiguration` to `Options` and property accessor methods (`getApplicationStringProperty`, `getApplicationBooleanProperty`) that return `Optional.empty()` when configuration is unavailable (build time). Wire `ApplicationConfiguration` from `DevModeInitializer`. Fixes #24055
|
Options for TypeScriptBootstrapModifier consumers (#24073)Options for TypeScriptBootstrapModifier consumers (#24073) (CP: 25.0)
|
Hi @mcollovati and @caalador, when i performed cherry-pick to this commit to 24.10, i have encountered the following issue. Can you take a look and pick it manually? |
|
Hi @mcollovati and @caalador, when i performed cherry-pick to this commit to 24.9, i have encountered the following issue. Can you take a look and pick it manually? |



TypeScriptBootstrapModifierimplementations (e.g., Copilot) need accessto application properties to conditionally modify bootstrap TypeScript. Currently, the Copilot script is injected in dev mode regardless of whether Copilot is enabled in the project configuration.
Add
withApplicationConfigurationtoOptionsand property accessor methods (getApplicationStringProperty,getApplicationBooleanProperty)that return
Optional.empty()when configuration is unavailable (build time). WireApplicationConfigurationfromDevModeInitializer.Fixes #24055