ga-wdi-boston / js-javascripting-study

JavaScript: javascripting Study

This study should be completed over multiple evenings.

NodeSchool is an excellent free and open-source resource for learning Node.js. We will use NodeSchool in the future to help us learn to learn how to develop APIs using Node.js. For now, we'll use the javascripting workshop to review what we've learned so far.

Prerequisites

• WDI Fundamentals

Objectives

By the end of this, developers should be able to:

• Recognize common, fundamental development patterns in JavaScript.
• Work with primitives, reference types, control flow, callbacks, and array methods.

Instructions

1. Fork and clone this repository.
2. Change into the new directory.
3. Create and checkout a new branch, named response.
4. Follow the directions given in study.md.
5. When finished, push to your fork and submit a pull request.

You may wish to refer to FAQs related to forking, cloning, and pull requests.

Tasks

Developers should run these often!

• grunt nag or just grunt: runs code quality analysis tools on your code and complains.
• grunt reformat: reformats all your code in a standard style.
• grunt test: runs any automated tests; may depend on grunt build.

License

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].

js-javascripting-study's Issues

Rename to js-javascripting-review?

A pull request isn't required. They typically are required for studies.

Use study template README layout

Update from study template

study.md disagress with README.md

study.md:

This study is for your benefit. We do not expect a pull request.

This is wrong. instructions in README.md are correct.

ga-wdi-boston/js-javascripting-study

.jshintrc and .jscrc missing from repo.

needed for use of use strict and jscs linter.

Should be pulled from most updated template, likely node.

Instructions

Make time frame for completion explicit.

N steps in M days.

Change this to a set of files for pull requests on the lessons?

I think Jeff and I discussed this but about learnyounode

.jshint and .jscsrc do not exist in this repo

Need to add the config files for the linters so things like 'Warning: Use the function form of "use strict"' do not pop up.

Clarify instructions: no pull request needed, no fork and clone necessary

Remove the first paragraph in "Optional Response"

Issues #2, #5, and #17 were not fully addressed. The first paragraph in the "Optional Response" section should be removed to be consistent with the rest of study.md and README.md

var instead of let

I am not sure if this is a big deal, but should we make this ask us to use let instead of var since that is what we are doing in class?

discrepancy of instructions between README and study.md

I didn't realize this myself until now, the readme asks for a standard pull request response, and the study.

We should clarify directions between the two to be more clear an uniform.