publiclab / matcher-cli

Node-based CLI utility for local matcher-core configs headless testing 🎈
GNU General Public License v3.0
1 stars 7 forks source link

Document filtering algorithm #11

Open rexagod opened 5 years ago

rexagod commented 5 years ago

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you πŸ’

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

  2. You can also edit files directly in your browser and open a pull request from there.

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

spassaro80 commented 5 years ago

Hi, can I pick this one?

thx

rexagod commented 5 years ago

Sure! Go ahead!

Pranshu Srivastava | @rexagod

On Thu, 29 Aug 2019, 18:15 spassaro80, notifications@github.com wrote:

Hi, can I pick this one?

thx

β€” You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/matcher-cli/issues/11?email_source=notifications&email_token=AIAAUZ7PU27JHTD7BRFD3JTQG7AEZA5CNFSM4IPOWGNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5OLATA#issuecomment-526168140, or mute the thread https://github.com/notifications/unsubscribe-auth/AIAAUZ5E2QF2YONDDWUW4ZTQG7AEZANCNFSM4IPOWGNA .

aishukamble commented 5 years ago

Hi, New contributor here. want to pick it.

rexagod commented 5 years ago

Sure! Go ahead!

Pranshu Srivastava | @rexagod

On Sat, 31 Aug 2019, 13:53 aishukamble, notifications@github.com wrote:

Hi, New contributor here. want to pick it.

β€” You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/publiclab/matcher-cli/issues/11?email_source=notifications&email_token=AIAAUZ6LHGQK27L6XTZWIL3QHIS6JA5CNFSM4IPOWGNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5TIDSY#issuecomment-526811595, or mute the thread https://github.com/notifications/unsubscribe-auth/AIAAUZ4XB42YG4MC753QC3TQHIS6JANCNFSM4IPOWGNA .

spassaro80 commented 5 years ago

Hi

I've tried to run matcher.js in node.js but it by it gives me this error. I'm sure I'm doing something wrong, I'll try to find what it is :).

Server's up @ http://127.0.0.1:9990

(node:7708) UnhandledPromiseRejectionWarning: Error: net::ERR_CONNECTION_REFUSED at http://127.0.0.1:9990/demo/ at navigate (C:\Users\00070261\matcher-cli\node_modules\puppeteer\lib\FrameManager.js:121:37) at process._tickCallback (internal/process/next_tick.js:68:7) -- ASYNC -- at Frame. (C:\Users\00070261\matcher-cli\node_modules\puppeteer\lib\helper.js:110:27) at Page.goto (C:\Users\00070261\matcher-cli\node_modules\puppeteer\lib\Page.js:629:49) at Page. (C:\Users\00070261\matcher-cli\node_modules\puppeteer\lib\helper.js:111:23) at invoke (C:\Users\00070261\matcher-cli\src\matcher-summon.js:56:14) at process._tickCallback (internal/process/next_tick.js:68:7) (node:7708) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:7708) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

SantruptaMishra98 commented 5 years ago

hi can I pick this up?

bermylle commented 4 years ago

Hi can i pick this up? Or is it already taken :)

stefanosu commented 4 years ago

Hi is this issue still being worked on? I would like to help if any is needed? Thanks, first-time contributor here.