[JS]General issue: ES6 Analysis Seems Unsupported
- 主要言語
- CodeQL
- スター
- 10.1k
- フォーク
- 2.1k
- 平均マージ
- 2日 15時間
- マージ済み PR(30日)
- 141
説明
## **ES6 Analysis Seems Unsupported**
When I use:
```javascript
const { chromium } = require('playwright');
// ... other code ...
const newBrowser = await chromium.launch({ headless: true });
```
The following CodeQL cannot track the variable `chromium`:
```ql
SourceNode playwright(TypeTracker t) {
t.start() and
(
result = globalVarRef("chromium")
or
result = moduleImport("playwright")
)
or
exists(TypeTracker t2 |
result = playwright(t2).track(t2, t)
)
}
SourceNode playwright() {
result = playwright(TypeTracker::end())
}
SourceNode playwrightLaunch(TypeTracker t) {
t.start() and
result = playwright().getAMethodCall("launch")
or
exists(TypeTracker t2 |
result = playwrightLaunch(t2).track(t2, t)
)
}
SourceNode playwrightLaunch() {
result = playwrightLaunch(TypeTracker::end())
}
```
However, if it is:
```javascript
const path = require('path');
// ... other code ...
path.join(...);
```
It works!
So, what should I do to track `chromium` in `{chromium}`?
Looking forward to your response.
コントリビューションガイド
調査の方向性
Start with the provided JavaScript destructuring example and the CodeQL entry points `globalVarRef("chromium")`, `moduleImport("playwright")`, and the `playwright` and `playwrightLaunch` predicates. Compare their behavior with the working `path.join(...)` example; done means the analysis tracks `chromium` from `{ chromium }` through `chromium.launch(...)`.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- javascript
- 領域
- security
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100