BridgeJS: Namespaced elements in Exports#468
Merged
krodak merged 1 commit intoswiftwasm:mainfrom Nov 19, 2025
Merged
Conversation
kateinoigakukun
approved these changes
Nov 19, 2025
Member
kateinoigakukun
left a comment
There was a problem hiding this comment.
The generated code is well aligned with my expectations, thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduction
First part of improvements to address #451 and discussions from: #448 (comment)
Overview
Object.definePropertynow only global this only references export's implementationTesting
Some additional tests to check extended exports access
Next steps
Next PR will include:
namespace global{ "exposeToGlobal": true }inbridge-js.config.json