Hi,

I'm the author of the "nbts" TypeScript Editor plugin (
http://plugins.netbeans.org/plugin/60605/typescript-editor,
https://github.com/Everlaw/nbts).

When I tested it in NetBeans 9.0 RC1, I saw major performance problems with
saving files, due to the change made to indexing in
https://netbeans.org/bugzilla/show_bug.cgi?id=270667. nbts needs to know
about all .ts files in a source root, so I return false from
CustomIndexerFactory#scanStarted - this used to only be applicable to the
initial scan when the root is first opened, but now it also affects live
changes. And on live changes, it affects ALL indexers! So, for example,
saving one .java file would end up recompiling the whole project.

I'll fix this in the next version of nbts (diff:
https://github.com/jeffreymorlan/nbts/commit/504f3dc6c7e721387b5597b66b0c0bc6fa30440b).
But, if someone using an existing version (<= 2.9.1.0) updates to NetBeans
9, they will get a severely degraded experience without the cause being
obvious.

Does NetBeans have a plugin blacklist that can prevent old versions from
being used?

(Also, was it really intentional that after the initial scan, scanStarted
returning false affects unrelated indexers?)

Thanks
Jeffrey

Reply via email to