Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
From: Kerri Shotts <kerrishotts@gmail.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_0AF981DF-A04B-40E8-B0D0-2238B248C3A4"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [DISCUSS] Plugin search is broken
Date: Fri, 24 Mar 2017 07:36:18 -0500
References: <CAE6O_-aRU+gEDGJt=g0ZiBYoJ1k_iTSzO4QyoRpH0yDFjch=1A@mail.gmail.com>
 <CAE6O_-ZLghVPbNeLEMeegh1=oM1XOkpJyGfbh0SEjTnQKRBWRg@mail.gmail.com>
 <CAE6O_-b8dhwaAP9F9oSRvNoVWpKPkrtFd2xm3R==S+W829eOpw@mail.gmail.com>
 <CAE6O_-Y7eXwmpZY8pE-O4aDtf9na48Oc9o8poOmyvXG6qdB7Wg@mail.gmail.com>
 <CAE6O_-bmgkVDKTAaL7rJvTOkw-eSm7LCwnO0k74UaFw7QuF5Sw@mail.gmail.com>
 <CAE6O_-aPR6z4zibopYARWkJQ5s=HnJnQHdtWQqOQ3koHaq7eCA@mail.gmail.com>
 <CAE6O_-Z_rs9w+Qe2uovFM09rfN7wConXs0wd8apDkNV8m-Uy1A@mail.gmail.com>
To: dev@cordova.apache.org
In-Reply-To: <CAE6O_-Z_rs9w+Qe2uovFM09rfN7wConXs0wd8apDkNV8m-Uy1A@mail.gmail.com>
Message-Id: <191F4C9D-18F6-482E-9939-24C540A664C6@gmail.com>
archived-at: Fri, 24 Mar 2017 12:36:28 -0000

--Apple-Mail=_0AF981DF-A04B-40E8-B0D0-2238B248C3A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1 to moving off npmsearch.

While I=E2=80=99m thinking of it =E2=80=94 where does the code for the =
plugin search live? I found variations on it, but not sure I ever came =
across the canonical version.

~ Kerri

> On Mar 23, 2017, at 16:04, Shazron <shazron@apache.org> wrote:
>=20
> I'm going to assume by lazy consensus that moving off npmsearch is a =
'go'.
>=20
> Filed: https://issues.apache.org/jira/browse/CB-12602
>=20
> Currently our plugin search works after I filed those two issues in =
their
> repo and they were was fixed, thus fixing our search.
>=20
> On Sun, Mar 19, 2017 at 4:36 PM, Shazron <shazron@apache.org> wrote:
>=20
>> Consequently, found another bug and filed: https://issues.apache.
>> org/jira/browse/CB-12585
>>=20
>> On Sun, Mar 19, 2017 at 4:04 PM, Shazron <shazron@apache.org> wrote:
>>=20
>>> I filed https://github.com/nodesource/npmsearch/issues/54 earlier =
and
>>> the dev fixed it right away, yay! So currently our search is working =
again,
>>> but the original proposal stands regarding migration.
>>>=20
>>> On Sun, Mar 19, 2017 at 1:50 PM, Shazron <shazron@apache.org> wrote:
>>>=20
>>>> Ignore the last message ;)
>>>>=20
>>>> This results in zero results.
>>>> http://npmsearch.com/query/?fields=3Dname,keywords,license,des
>>>> cription,author,modified,homepage,version,rating&q=3Dkeywords:
>>>> %22ecosystem:cordova%22&sort=3Drating:desc
>>>>=20
>>>> The same URL without the sort query param has results:
>>>>=20
>>>> http://npmsearch.com/query/?fields=3Dname,keywords,license,des
>>>> cription,author,modified,homepage,version,rating&q=3Dkeywords:
>>>> %22ecosystem:cordova%22
>>>>=20
>>>>=20
>>>> On Sun, Mar 19, 2017 at 1:44 PM, Shazron <shazron@apache.org> =
wrote:
>>>>=20
>>>>> I believe the original problem lies in npmsearch.com erroring on a
>>>>> query param "sort":
>>>>> http://npmsearch.com/query/?sort=3Drating:desc&fields=3Dname,key
>>>>> words,license,description,author,modified,homepage,version,r
>>>>> ating&sort=3D&q=3Dkeywords:%22ecosystem:cordova%22
>>>>>=20
>>>>> The URL above is a query that we send to it. (a simple "sort=3D" =
results
>>>>> in the same error)
>>>>>=20
>>>>> If "sort" is removed, it is fine:
>>>>> http://npmsearch.com/query/?fields=3Dname,keywords,license,des
>>>>> cription,author,modified,homepage,version,rating&sort=3D&q=3Dkey
>>>>> words:%22ecosystem:cordova%22
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Sun, Mar 19, 2017 at 1:25 PM, Shazron <shazron@apache.org> =
wrote:
>>>>>=20
>>>>>> The impetus for this is, users are reporting [1][2][3][4] that =
they
>>>>>> can't find plugins, and I don't think they know of a search =
alternative.
>>>>>>=20
>>>>>> In the near term, I think we should tweet how to search for =
plugins
>>>>>> using npmjs.com
>>>>>>=20
>>>>>> [1] https://twitter.com/edeortuzar/status/843310576101146625
>>>>>> [2] https://twitter.com/kumakumadev/status/843149557127155712
>>>>>> [3] https://twitter.com/quangv/status/842925319254360064
>>>>>> [4] https://twitter.com/skumarSDsoft/status/842677001433497600
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On Sun, Mar 19, 2017 at 1:19 PM, Shazron <shazron@apache.org> =
wrote:
>>>>>>=20
>>>>>>> ### PROBLEM
>>>>>>>=20
>>>>>>> Plugin search is broken.
>>>>>>>=20
>>>>>>> ### DESCRIPTION
>>>>>>>=20
>>>>>>> Page:
>>>>>>> http://cordova.apache.org/plugins/
>>>>>>>=20
>>>>>>> JIRA:
>>>>>>> https://issues.apache.org/jira/browse/CB-12579
>>>>>>>=20
>>>>>>>=20
>>>>>>> Q: How does the plugin search work?
>>>>>>>=20
>>>>>>> A:
>>>>>>> Page Source: http://cordova.apache.org/plugins
>>>>>>> and the source (this specific line): http://svn.apache.org/v
>>>>>>> iewvc/cordova/site/public/plugins/index.html?view=3Dmarkup#l117
>>>>>>>=20
>>>>>>> which is added from here:
>>>>>>> https://github.com/apache/cordova-docs/blob/master/www/plugi
>>>>>>> ns/index.html
>>>>>>>=20
>>>>>>> which is generated from this React code:
>>>>>>> https://github.com/apache/cordova-docs/blob/a3589ce66336821f
>>>>>>> 2fd714a1115125cfcfa9fd1b/www/static/plugins/app.js
>>>>>>>=20
>>>>>>> Nothing shows up as errors in the Web Inspector, so it is hard =
to
>>>>>>> track down.
>>>>>>>=20
>>>>>>> ### MY PROPOSAL
>>>>>>>=20
>>>>>>> The era of needing npmsearch.com to populate this page is over. =
We
>>>>>>> could just redirect users to npmjs.com and add the
>>>>>>> "ecosystem:cordova" token (i.e https://www.npmjs.com/sea
>>>>>>> rch?q=3Decosystem%3Acordova)
>>>>>>>=20
>>>>>>> The alternative is to use npm's Registry API:
>>>>>>> =
https://github.com/npm/registry/commits/master/docs/REGISTRY-API.md
>>>>>>>=20
>>>>>>> The API was only documented earlier this year, if not we would =
have
>>>>>>> used it.
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20


--Apple-Mail=_0AF981DF-A04B-40E8-B0D0-2238B248C3A4--