andrewsuzuki / elm-todo-rest-api Goto Github PK

If you create a todo like this:

POST /todos

{
  "title": "1234",
  …
}

The response will be:

{
  "title": 1234,
  …
}

This breaks the todoDecoder, which expects title to be a string. Even more confusingly, the Result.Err from FetchAllDone and CreateDone are discarded as well. Maybe consider reporting upstream and/or making a more type-friendly API.

Set up a gh-pages branch with a demo site.

Use programWithFlags along with webpack environment variables to substitute the local endpoint for http://jsonplaceholder.typicode.com/todos. It mostly works as-is, except (1) it isn't persistent, (2) POSTs always return the same id, so only one todo can be created, and (3) it's pretty slow. Better than nothing though.

Greetings!

Not sure you're interested, but I wanted to mess around with this app to see a working Elm client with a JSON API, and also wanted to learn the differences in Elm 0.19. I forked and upgraded, a bit with elm-upgrade and then some code changes to accommodate the things it couldn't upgrade for me. If you're interested I can either submit a PR or just grab it if you'd like.

Cheers!

I cloned this repository, run npm run api and npm run dev, but it's throwing an error.

app.js:7535 Uncaught Error: Cannot find module "./Main.elm"webpackMissingModule @ app.js:7535(anonymous function) @ app.js:7535__webpack_require__ @ app.js:20(anonymous function) @ app.js:48__webpack_require__ @ app.js:20(anonymous function) @ app.js:40(anonymous function) @ app.js:43

app.js:99 [WDS] Errors while compiling.

app.js:101 C:\Users\lluis\Source\Repos\elm-todo-rest-api-master\elm-todo-rest-api-master\node_modules\elm-webpack-loader\node_modules\node-elm-compiler\worker.js:96
  errorMessage += `
                  ^
Unexpected token ILLEGAL
 @ ./src/index.js 7:10-31