Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document filtering algorithm #11

Open
5 tasks
rexagod opened this issue Aug 26, 2019 · 8 comments
Open
5 tasks

Document filtering algorithm #11

rexagod opened this issue Aug 26, 2019 · 8 comments
Labels

Comments

@rexagod
Copy link
Member

rexagod commented Aug 26, 2019

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

  • 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

  • 📝 Update: Add to README the process the algorithm that's used to detect and filter commands below. We recommend you to run the library and set up breakpoints to familiarize yourself with this!

    matcher-cli/matcher.js

    Lines 27 to 38 in 0bf7186

    async function vorpalify(args) {
    const {query} = args;
    // eslint-disable-next-line no-unused-vars
    const summoner = await commands.summoner;
    if (eval(`commands.${query}`) !== undefined) {
    eval(`commands.${query}()`);
    } else if (eval(`summoner.${query}`)) {
    console.log(eval(`summoner.${query}`));
    } else {
    error(`Invalid command: "${query}", exiting...\n`);
    process.exit();
    }

  • 💾 Commit your changes

  • 🔀 Start a Pull Request. There are two ways how you can start a pull request:

  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.

  • 🏁 Done Ask in comments for a review :)

🤔❓ 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
Copy link

Hi, can I pick this one?

thx

@rexagod
Copy link
Member Author

rexagod commented Aug 29, 2019 via email

@aishukamble
Copy link

Hi, New contributor here. want to pick it.

@rexagod
Copy link
Member Author

rexagod commented Aug 31, 2019 via email

@spassaro80
Copy link

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
Copy link

hi can I pick this up?

@bermylle
Copy link

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

@stefanosu
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants