Motivation: as someone on the reviewer side, I want to check out submissions even those I'm not assigned as the reviewer: to check out a particularly good solution, or a solution using a particular framework. However, downloading from S3 and opening the file involves too many clicks and keystrokes.

It'd be nice if the take-home server can serve up submissions.

For zip submissions: zip.js https://gildas-lormeau.github.io/zip.js/

My feeling is that way to build native modules as described in the wiki don't work with elm 0.17+? Is that true?

I was reminded of them as i got up to date on Elm Town but my first attempts to build code based on these examples ran into Elm.Native is not defined

It's important that I be notified / subscribed when a new take home is created.

Not sure how we're doing it on the open source version of the tool but on our implementation we need a way to define default subscribers to the issue 👍

Reading through “Native best practices”, I was confused by the following sections:

Use always to ensure that your Tasks are wrapped appropriately.

See https://github.com/elm-lang/core/issues/453#issuecomment-161050745

Denote impure functions with Task

There's no real way outside of Tasks to signify when a function is impure in Elm. Using units () to signify when a function should run and do something with a side effect allows people to easily identify side effects.

activeElement : () -> Task x QueryNode
activeElement =
    Native.Query.activeElement

@rtfeldman points out that one may discover an incorrectly constructed Task by observing its behaviour in two scenarios:

1. When given as a parameter to always;
2. When suspended in an anonymous function that ignores its parameter.

(The latter idiom is known as delay in Scheme, SML and Idris, as lazy in OCaml, and as defer in PureScript.)

I think this guide would benefit from an example of constructing a Task correctly, such as the one given in the linked discussion.

@jvoigtlaender gives the JavaScript part: (https://github.com/elm-lang/core/issues/453#issuecomment-161041092)

const readFileAndLog = function (path) {
  return Task.asyncFunction(function (callback) {
    fs.readFile(path, function(err, data) {
      if (err) {
        throw err;
      } else {
        console.log("data: ", data);
      }
    });
    return callback(Task.succeed(Utils.Tuple0));
  });
};

@Fresheyeball gives the Elm part: (https://github.com/Fresheyeball/isolating-task-bug/blob/asyncFunction-solution/OK.elm)

readFileAndLog : String -> Task x ()
readFileAndLog = Native.FS.readFileAndLog

The advice to “use [() as an additional parameter] to signify when a function should run and do something with a side effect” seems misleading, if we assume that a Task already represents an effectful computation.

Thoughts?

Right now, it says:

• Start time
• End time
• Time remaining

Instead, it should just say:

• Start time
• Time it should take to complete

Right now I'm using a dump of elm-css from master from before things were rewritten. We want to be on the latest version of elm-css, which should be a simple upgrade. It'll look something like this:

• Update the elm-css folder to have the latest dump of non-test stuff from here
• Ensure it compiles and fix any compile errors

In theory, it should be a trivial upgrade.

I mentioned this to @dui some time ago: suppose I know my friend Sam Quayle is applying, and I get assigned a take home for "SQ". Suddenly I have to worry about bias.

Would be nicer if I got assigned a take-home for "ac9bfg2" or something similar. 😉

To prevent a take-home test from being updated when someone's in progress, take-home server should serve a specific version of the take-home problem to each candidate.

(=>) = (,)

Hi guys,
This repo contains a lot of goodies; the http server, NeDB bindings and more.
Any plans into publishing parts of this separately so one can just do elm package install NoRedInk/elm-http-server?

PS: amazing work, thank you!

Right now, if a user doesn't submit a file, then it will still count as submitted and upload nothing.

Instead, we want to warn and not let people submit when there's no file selected.

The core logic on the server side is here - https://github.com/NoRedInk/take-home/blob/master/instance/server/Generators.elm#L86

But it should be checked client side if possible, here - https://github.com/NoRedInk/take-home/blob/master/instance/server/Client/StartTakeHome/Views.elm#L76

Note that right now, that view is a statically rendered view

It would be awesome if you can get rid of Amazon here so everyone can just run this to see how things works.

I know that you do not develop it for people as an example but it would be awesome if you'll find time to do this.

failed with 'FailedConnectionException "github.com" 443' when sending request to
http://github.com/evancz/virtual-dom/zipball/2.1.0/
/home/az/justforfun/ELM/take-home/instance/server/main.js:1
(function (exports, require, module, __filename, __dirname) { Elm.worker(Elm.Main);
^

ReferenceError: Elm is not defined
at Object. (/home/az/justforfun/ELM/take-home/instance/server/main.js:1:63)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:139:18)
at node.js:999:3

Right now, we have files like this one - https://github.com/NoRedInk/take-home/blob/master/instance/server/Client/StartTakeHome/Views.elm which contains views which are both used with writeNode, which is the server-side rendering call, and writeElm, which sends things down with an attached Elm runtime. They should be in a separate file, so it's clear which ones are server-side rendered.

A general issue. At the moment, there is little to no styling on any of the pages.

At the moment there are no suggested styles - other than the colours should probably match NRI colours

Motivation

We need to find out use cases of elm-css and how it feels to work with! This project could potentially be the largest use case of elm-css.