tawn33y

A few recommended community guidelines on opening PRs for good code quality on the whatsapp-cloud-api repo:

• Open a new branch from staging (not main) with the prefix feature/ISSUE-XX, where XX is the issue number, e.g. feature/ISSUE-10
• Make your changes and add tests for them.
• Run the linter, ensure all tests pass, and then create a build. See more under the Development docs.
• Ensure the build size does not substantially grow the currently published size on the npmjs.com page. You can run npm pack to verify the new package size, then look at the Properties of the created tgz file.
• Commit the changes with a well descriptive message with the format: feature/ISSUE-XX Some message here, e.g. feature/ISSUE-10 Add logging when starting an express server
• Open a PR to the staging branch with the title format feature/ISSUE-XX Some message here, e.g. `feature/ISSUE-10 Add logg

tawn33y

const isValidSudoku = (board) => {
    const obj = { 
        rows: {}, // 9 rows, each containing 9 cells across
        columns: {}, // 9 columns, each containing 9 cells down
        blocks: {}, // 9 blocks, each containing 3x3 cells inside
    };
    
    let isValid = true;
    
    loop1:

tawn33y

const isPalindrome = (x) => {
  if (x < 0 || (x % 10 === 0 && x !== 0)) {
    return false;
  }
  
  return x === reverse(x);
};

const reverse = (num) => {
  let rev = 0;

tawn33y

// To run the code, uncomment the following:
// console.log(generateGrid());
// console.log(test(50));

// --------------------------------------------------------------------------------
// helper functions
// --------------------------------------------------------------------------------

export const sum = (...arr) => arr.reduce((acc, curr) => {
  acc += curr;