tvl-depot/client
William Carroll b9ed4a2dc1 Partially support federated login
Two things:
1. I've never attempted to support this before.
2. It seems surprisingly and perhaps deceptively simpler than what I
   expected. I'm unsure what to do once Google's API authenticates the user. I
   currently look-up the user's role, trips, etc. using their email address. The
   role is stored in the Accounts table alongside username, email, password. I
   will speak with the interviewer tomorrow about this.
2020-08-02 21:27:08 +01:00
..
src Partially support federated login 2020-08-02 21:27:08 +01:00
.gitignore Add Elm boilerplate to project 2020-07-29 09:51:18 +01:00
dir-locals.nix Support a basic client-side login flow 2020-07-31 18:57:35 +01:00
elm.json Support creating Trips from the frontend 2020-08-01 23:04:06 +01:00
index.css Support creating Trips from the frontend 2020-08-01 23:04:06 +01:00
index.html Partially support federated login 2020-08-02 21:27:08 +01:00
print.css Support printing user's itinerary 2020-08-02 14:23:38 +01:00
README.md Support a basic client-side login flow 2020-07-31 18:57:35 +01:00
shell.nix Support a basic client-side login flow 2020-07-31 18:57:35 +01:00

Elm

Elm has one of the best developer experiences that I'm aware of. The error messages are helpful and the entire experience is optimized to improve the ease of writing web applications.

Developing

If you're interested in contributing, the following will create an environment in which you can develop:

$ nix-shell
$ npx tailwindcss build index.css -o output.css
$ elm-live -- src/Main.elm --output=Main.min.js

You can now view your web client at http://localhost:8000!