Łukasz Lityński

what is more weird, isNodeCollapsed is used only once in the library and it doesn't seem to be actually used: https://github.com/pqx/react-ui-tree/blob/6d48ca6d7a7df86655c9a679bc4be3451e0391e5/lib/react-ui-tree.js#L31 Maybe I am wrong, but it looks for me...

So on your installation you can't also running tests? Because I wanted to add a feature. I made a preview feature for React elements: https://github.com/princejwesley/Mancy/pull/117 (no tests for now).

Well. I understand your concerns. For plugins which modify tree and want to have access to scope this could raise some problems. But for me this won't be a problem,...

Virtual AST types :) Thanks. I didn't know I could do this way. I tried your tip, and it worked :) But then I've decided to make some bigger changes...

> quite a different concept of how scope is generated, it's basically built from bubbling up > references/declarations capturing them when a scope boundary is hit. I don't really understand...

What's this? This code looks like some Python related config file, not related to this repository.

`not sure what part is causing the poor performance.` analysis is done in different repo and it performs advanced static analysis, so it can take long. But it should be...

I've optimized a little bit. - cached some objects which was created constantly during analysis. It should help Atom to be responsive. Also it has decreased indexing time when I...

I've made another optimization. Previously analyzing was triggered in setInterval (every 1000 miliseconds). This was unecessary and caused e.g. lags when document was scrolled. Now analyzing is triggered only after...

I've added option in settings for disabling "panel": `Should Show Types` and I've added option for sorting (by type or by position in file).