search

clearlydefined / website

Website for clearlydefined.io
https://clearlydefined.io
MIT License
26 stars 29 forks source link

Repository-specific string match #158

Open fossygirl opened 6 years ago

fossygirl commented 6 years ago

Users should be able to preface their search strings with the name of a known component type or provider (e.g., github:, npm:, npmjs:, …) and have the search results restricted to just those types or providers.­

storrisi commented 5 years ago

This is not yet in place but probably the new implementations of definitions query builder on the service could help to fullfill this requirement.

storrisi commented 5 years ago

@dabutvin could you confirm that using some of the params exposed from the definition API, we are able to make query like the one specified? I guess it could be enough to pass a provider= param together with the string

dabutvin commented 5 years ago

good point @storrisi

@fossygirl do you still want to light up this kind of syntax in the current state of things? Is this specifically for https://clearlydefined.io/definitions ?

storrisi commented 5 years ago

@fossygirl any updates on this?

fossygirl commented 5 years ago

@jeffmcaffer probably has thoughts here.

gianpaj commented 5 years ago

For the future reference, if we search "Query Parser Syntax github" on Google. There are plenty of JS repo we could use to parse the text field and get for example this parsed provider:npm jquery license:none

For the first implementation we agreed on only providing a search by provider, therefore the above "Query Parser Syntax" might be overkill for a single search parameter

storrisi commented 5 years ago

@fossygirl may I ask you an update on this? Do we still need this implementation considering the current state of things?