Fix onhostcontextchanged handler invocation in examples
#351
+16
−12
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.
App.onhostcontextchangedis a setter-only property with no getter. TypeScript doesn't prevent reading from setter-only properties, soapp.onhostcontextchanged?.(ctx)compiles but silently returnsundefinedat runtime.Extract the handler into a named
handleHostContextChanged()function and call it directly afterconnect(), matching the pattern used inbasic-server-vanillajsand other examples.