Parsing Awesome-Hacking-Spots markdown?

[Alex Keyes]

Do you guys have suggestions for coming with a good way to parse through this document? I don't want to change the format of anything since that means we won't be able to have new PRs updated in the document. I was wondering if anyone could recommend a way to proactively parse through the README

[Richard Littauer]

Can you specify the requirements a bit more? wooorm/remark is one of the better markdown parsers out there, which may work for this, but there's a bit of a learning curve.

[Alex Keyes]

So I was thinking that we'd need to have a parser that could search by either city or country that would return a list of the locations under that subheading. I am thinking a simple text search for Matching the search with a name of a location on the document would be good.

…

On Dec 4, 2017 09:58, "Richard Littauer" ***@***.***> wrote: Can you specify the requirements a bit more? wooorm/remark <https://github.com/wooorm/remark> is one of the better markdown parsers out there, which may work for this, but there's a bit of a learning curve. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKQFrCAxV0xYJNR-q-o273AQZJqbpyRks5s9AiRgaJpZM4Qz_WK> .

[Richard Littauer]

How does this improve on the browser's native search?

[Alex Keyes]

It doesn't. I wanted to build a frontend for our readme list. Something like the Homebrew cask website. I'm asking about the best way to implement the functionality of the search page on that site. It uses the GitHub API and parses through the tree of committed files for packages. Obviously we can't do that since we have one big file so I was looking for suggestions on the best way to search our big markdown file.

…

On Dec 4, 2017 10:04, "Richard Littauer" ***@***.***> wrote: How does this improve on the browser's native search? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKQFnWY923TW2gIyQXf8-o-NBZoqAjxks5s9An9gaJpZM4Qz_WK> .

[Richard Littauer]

It looks like it should be trivial to implement their search directly. You can use basic regexes to search for cities with headings in the regex - ## Bogota, for instance, or just use plain text and see if our mileage varies.

Might be worth setting up a second GitHub repo for this, too. You could also use some GitHub database workflow, like opensourcedesign does, or octonews (unreleased, more work to do) will.

[Alex Keyes]

FWIW I've already set up a second branch on my local version of the repo. IIRC Github pages can work for either a separate branch or a separate repo. Thanks for the advice I was thinking that a plaintext regex search of the document is probably the best way to go but I like having someone to bounce ideas off of, you know?

…

On Mon, Dec 4, 2017 at 10:20 AM, Richard Littauer ***@***.***> wrote: It looks like it should be trivial to implement their search directly <https://github.com/caskroom/caskroom.github.io/blob/master/js/search.js>. You can use basic regexes to search for cities with headings in the regex - ## Bogota, for instance, or just use plain text and see if our mileage varies. Might be worth setting up a second GitHub repo for this, too. You could also use some GitHub database workflow, like opensourcedesign <https://github.com/opensourcedesign/opensourcedesign.github.io> does, or octonews <https://github.com/octonews/octonews> (unreleased, more work to do) will. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKQFkTHEGq4LSWUibKLl_s-9M4LJFALks5s9A2ngaJpZM4Qz_WK> .

-- Alex Keyes Phone: [phone] Calendar: https://alexkeyes.youcanbook.me www.alexkey.es