The following screenshot shows javascript call tree 🌲 of variable `browser` insides a closure. This feature is similar to incoming & outgoing calls from LSP. It is designed for the symbol analysis.
The screenshot below shows javascript call tree 🌲 for variable `browser` within a closure. This feature parallels the LSP 'incoming & outgoing calls' feature. It is designed for the symbol analysis.
- The first line of floating windows shows there are 3 references for the symbol <spanstyle="color:red">_browser_</span> in closure.js
- The topmost entry in the floating window indicates there are 3 references for the symbol <spanstyle="color:red">_browser_</span>within closure.js
- The first reference of browser is an assignment, an emoji 📝 indicates the value is changed in this line. In many
- The first reference of browser is an assignment, an emoji 📝 indicates the value is modified in this line. In many
cases, we search for references to find out when the value changed.
cases, we search for references to find out when the value changed.
- The second reference of `browser` is inside function `displayName` and `displayName` sit inside `makeFunc`, So you
- The second reference of `browser` is inside function `displayName` and `displayName` sit inside `makeFunc`, So you
will see `displayName{} <- makeFunc{}`
will see `displayName{} <- makeFunc{}`
- The third similar to the second, as var browser is on the right side of '=', the value not changed in this line
- The next occurrence of `browser` is located within the function `displayName`, which is nested inside `makeFunc`. Hence, the display reads `displayName{} <- makeFunc{}.`
and emoji is not shown.
- The final reference is akin to the previous one, except that since `browser` appears on the right side of the `=`, its value remains unaltered, and consequently, no emoji is displayed.