Fix DynamicLayoutComponent Initialization for Remote Environment Configurations and Remove Non-Null Assertion #23458
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.
Description
This pull request addresses an issue where applications that dynamically resolve their environment configuration via
removeEnv
encounter a runtime error:Cannot read properties of undefined (reading 'responseType')
. It also removes a non-null assertion frominject(DynamicLayoutComponent, { optional: true, skipSelf: true })
, due to it beingoptional
.OnInit
lifecycle hook with an environment change listener.getLayout()
is triggered only when theoAuthConfig
is available and itsresponseType
iscode
, preventing access to undefined propertiesgetLayout()
is triggered only whenlayout
is not initialized, preventing re-initialization of the layout.Checklist