repro:
go to npm, right-click. Wait for new package installer to load up.
in the search box type require-directory
result:
hundreds or results back.
require-directory *is* in the list but it's a long way down.
thoughts:
This is a particularly bad example as the word "require" is so common but it looks like it's not treating the input string as a single keyword and it's returning results even if only the first part of the keyword matches any part of a package description.
desired result.
if there's an exact match to the package name, promote this result to the top and tell the user something like "exact match found"
optional
- add a "see more results" option to show the remainder.
- enable search options to limit to package names only or similar.
Comments: Hi scrom, thanks for the feedback. Poor filtering/sorting of hyphenated search has been fixed in [changeset 5db13222aae9](https://nodejstools.codeplex.com/SourceControl/changeset/5db13222aae9d2a81f1cee29d73cbe5115cc6443), and is available in our latest dev build. Let us know if the behavior works better for you now. Re: the install package button, you're right - the button probably shouldn't be active while you're in the text box. I've opened a separate issue to track it here: https://nodejstools.codeplex.com/workitem/1692 Re: manually specifying a package name, are you referring to the behavior in beta 1 where the first result used to simply install the package name that you had typed into the search box? We made a design decision to simplify the UI because we had far too many bugs being filed on the dialog that boiled down to UI issues where it was trying to do too much by catering to both basic and advanced scenarios. So we split it up into the install packages dialog, which lets you browse/install packages and the .npm command in the repl window, which is preferred when you know exactly what package and package parameters you're searching for. Link to the latest dev build with improved filtering behavior - would love to hear your thoughts. https://nodejstools.codeplex.com/releases/view/213463
go to npm, right-click. Wait for new package installer to load up.
in the search box type require-directory
result:
hundreds or results back.
require-directory *is* in the list but it's a long way down.
thoughts:
This is a particularly bad example as the word "require" is so common but it looks like it's not treating the input string as a single keyword and it's returning results even if only the first part of the keyword matches any part of a package description.
desired result.
if there's an exact match to the package name, promote this result to the top and tell the user something like "exact match found"
optional
- add a "see more results" option to show the remainder.
- enable search options to limit to package names only or similar.
Comments: Hi scrom, thanks for the feedback. Poor filtering/sorting of hyphenated search has been fixed in [changeset 5db13222aae9](https://nodejstools.codeplex.com/SourceControl/changeset/5db13222aae9d2a81f1cee29d73cbe5115cc6443), and is available in our latest dev build. Let us know if the behavior works better for you now. Re: the install package button, you're right - the button probably shouldn't be active while you're in the text box. I've opened a separate issue to track it here: https://nodejstools.codeplex.com/workitem/1692 Re: manually specifying a package name, are you referring to the behavior in beta 1 where the first result used to simply install the package name that you had typed into the search box? We made a design decision to simplify the UI because we had far too many bugs being filed on the dialog that boiled down to UI issues where it was trying to do too much by catering to both basic and advanced scenarios. So we split it up into the install packages dialog, which lets you browse/install packages and the .npm command in the repl window, which is preferred when you know exactly what package and package parameters you're searching for. Link to the latest dev build with improved filtering behavior - would love to hear your thoughts. https://nodejstools.codeplex.com/releases/view/213463