bootcamperscollective / coders-workshop Goto Github PK

Add ESLint

In the main level:

• Run npm install eslint --save-dev
• Add .eslintrc config file
• Add .eslintignore config file

Match the styling as closely as possible, use .prettierrc to get a feel for the formatting style and rules.

For arrow functions, following best practices, there should always be parentheses included around an argument.
Consider changing "arrowParens": "avoid" in .prettierrc

The current license attributes copyright for everything to @andy-young. While he totally deserves the credit for running the show, I wonder if that can be adjusted. Licensing is complicated, so I'm not sure how to go about it.

Hi, this was from tonight's meeting. It was suggested to create a PR, but I wasn't sure where it should go. Which folder would be best?

const isPermPalin = str => {
  let m = new Map();
  for (c of str) {
    if(m.has(c)) {
      m.set(c, m.get(c)+1);
    } else {
      m.set(c, 1);
    }
  }
  let oddCount = 0;
  m.forEach((v,k) => {
    if (v % 2 === 1) {
      oddCount++;
    } 
  });
  return oddCount < 2;
}

console.log(isPermPalin('tactcoa')); // true
console.log(isPermPalin('racecar')); // true
console.log(isPermPalin('aaabbcc')); // true
console.log(isPermPalin('kitten')); // false

Make a function update(coordinate), which takes an integer representing somewhere within the boundaries of the <canvas> element (500px by 500px).

The function will need to randomly offset its given location by a short amount, say -2 to 2 pixels for every 30 milliseconds. This gives the sprite an appearance of sporadic buzzing.

Please rename master to main.

To do this easily, run these two commands:

git push origin master:main
git push origin :master

Should solutions to challenges be put in solutions folders alongside the challenges themselves?

Pros

• Easy to navigate between the challenge itself and the solution(s) to it
• Easy to navigate between different solutions to compare approaches

Cons

• Harder to track contributions per developer

• Jest test suite doesn't run because of an error in the package.json
• Install Jest for the repo as a devDependency

• Make sure @andy-young and @bry-an are admins in the organization
• Transfer ownership
• Add @bry-an and @MartinRosenberg to the team for the repo