]
Gorkem Ercan updated ERT-173:
-----------------------------
Sprint: devex #114 May 2016
Need to find a better solution for npm dependencies content assistant
[EBZ#492192]
----------------------------------------------------------------------------------
Key: ERT-173
URL:
https://issues.jboss.org/browse/ERT-173
Project: Eclipse Release Train
Issue Type: Task
Components: WTP Source Editing
Reporter: Friendly Jira Robot
Labels: bzira, wst.json
In order to show content assist proposals for npm dependencies a 3rd party web service
was used. It was a really problematic due to its unstable work, slowness and a tendency to
change an URL for requests and formats of response.
I do believe, we should not provide any content assist for dependencies in case no search
pattern is provided (typed in) by a user because of really huge memory requirements and
network overload in such case:
- Native "npm search" command fails to list all the available packages on my
environment after about 5 minutes of downloading packages
Given this, IMHO, we have not to show *all* available packages in content assistant, but
show package list only if at least first letter (or a couple of beginning letters) of
package name is typed in by a user.
Also the way to get the proposals itself is also a question: we cannot rely on 3rd party
services as they are not enough stable and fast.