learn-co-curriculum / js-task-list

Task Lists

Description

In this lab, you'll be creating a simple JavaScript task list. You've been provided with the HTML skeleton, but will need to implement the JS code in the js/tasklist.js directory.

You can see a working copy live at: http://jongrover.github.io/task-list/

Bonus

1. Add jQuery UI Sortable to the list so that tasks can be dragged and dropped to reorder.

View Task Lists on Learn.co and start learning to code for free.

js-task-list's Issues

Incomplete.

Github Pages link 404s

Canonical is at: https://github.com/learn-co-curriculum/js-task-list

but the students copy is somehow aliased to : https://github.com/learn-co-students/task-list-fe-1015

notice the js- is missing and the students copy is now just task-list

The Github pages site should be at: http://learn-co-curriculum.github.io/js-task-list this 404s

THe README lists http://learn-co-curriculum.github.io/task-list this also 404s

Joe suggested issue was related to a CNAME taken by student project...

Integrate Jasmine Test Suite Found in wip-jasmine-tests

The branch wip-jasmine-tests was an experiment in integration HTML and JS through a Jasmine test runner that is compatible with the Learn CLI or some sort of test runner.

About Javascript Testing

The concept here was to load their HTML from their lab as a fixture in the test suite - so instead of having the test suite use an HTML file for the document to allow us to test jQuery, when we run the JS test suite, we would actually use the student's file as the fixture. However, this creates an issue as Chrome will not allow you to read from a local file unless you start Chrome with local-file-access as described in the branch's readme.

You could get around this by starting chrome with the following command described in the README.

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --allow-file-access-from-files

That is not an acceptable solution as it is very unreliable. You can see the failure of Chrome to properly run the test suite in the test runner's HTML.

When run entirely through the command line though, not a browser based runner (which I believe would be ideal), we don't get that error but get actual code errors (sort of it seems the runner is even broken).

DO NOT MERGE or attempt to fix this without talking to me.