adil1214

user1
password1
user2
password2
user3
password3
user4
password4
user5
password5

adil1214

// converting circular structure to json
// source: https://stackoverflow.com/a/48254637/8717257
const customStringify = function (v) {
  const cache = new Set();
  return JSON.stringify(v, function (key, value) {
    if (typeof value === 'object' && value !== null) {
      if (cache.has(value)) {
        // Circular reference found, discard key
        return;
      }

adil1214

    There is no way to store an empty object/array/null value.
    There are also no actual arrays.  Array values get stored as objects with integer keys.
        (If all keys are integers, it will be returned as an array.)

    Basically, it's one giant tree of hashes with string keys.
    Simply write a value to any location, and the intermediary locations will automatically come into existance.

 ── Classes ──

    DataSnapshot  : Container for a subtree of data at a particular location.

adil1214

/*
// egghead playlist 
// https://egghead.io/courses/advanced-react-component-patterns
*/

let a = 0;

[...document.getElementsByClassName('w-100 pa1 tl mv0 flex flex-row items-center no-underline dark-gray h2')]
  .map((e) => e.innerText )
  .forEach((d) => 

adil1214

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

adil1214

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

adil1214

/*input
3 3
1 3 4
2 2 3
1 2 4
*/

// expected output is 60
 
#include <bits/stdc++.h>

adil1214

# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so

# Packages #

adil1214

## How to hide API keys from github ##

1. If you have already pushed commits with sensitive data, follow this guide to remove the sensitive info while 
retaining your commits: https://help.github.com/articles/remove-sensitive-data/

2. In the terminal, create a config.js file and open it up:

touch config.js
atom config.js