pschmied / do-some-things-in-js Goto Github PK

Once you've done #6 , tell me to modify the README. Do so by opening an issue in this repository and assigning it to me. Remember: you have NOT pushed your README changes to github... yet.

Reference:
https://github.com/settings/keys

Depends on #1 . Do that first. Clone via SSH not HTTPS.

this is for the js-calisthenics exercise

Take a look, let me know if it's in line with what you were expecting. Also, I'd like to know how you might've approached it. I have never done or even really looked at any unit tests before, so I went by my own judgement.

Modify the readme with your own change. I suspect there's a lesson in here about merging conflicts...

Nobody likes being pestered about editor autosave files and other ephemera. See if you can dig up the default javascript gitignore from github... it might have useful suggestions.

You can make it a README.md or a README.org. Content doesn't matter for now. Just add some text. It can say anything.

There's a method to this madness.

Create a javascript collection (or generating function) that contains all integers in the range 0-99999.

Create a function that will, when given the input created above, return the sum of all odd integers in the collection.

Put this code in a file in an appropriately named directory with a readme explaining how the hell I run your code. ;-)

#9 likely caused a merge conflict.

DON'T PANIC

As the one who encounters the merge conflict, you have to fix it. But you also get to decide how it gets fixed. So... rock and roll.

Some hints:

• you'll need to "pull" the offending changes from the remote repo on github to be able to merge
• there are fancy graphical diffing utilities, but you should probably also know how to open a text editor and see the stuff git adds to show you where conflicts are, and also understand that you simply have to make the conflicted file look like you want.
• Once your file looks like you want, commit it and push it per normal.