swiftwasm / swiftwasm/JavaScriptKit
BridgeJS: Add diagnostics for unsupported `from: .global` / `from: .module(...)` parameters for imported symbols
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 986
- Forks
- 76
- Avg merge
- 21h 11m
- Merged PRs (30d)
- 4
Description
BridgeJS only supports the .from in top-level decls for @JSClass, @JSFunction and @JSGetter. In other places (eg: class members) the specified JSImportFrom is essentially ignored.
we should add diagnostics instead of ignoring invalid from parameters.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing BridgeJS handling of @JSClass, @JSFunction, and @JSGetter declarations and their imported symbols. Check how JSImportFrom is processed for top-level declarations and class members; done means unsupported .global and .module(...) parameters produce diagnostics instead of being ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100