https://github.com/ravicious/flux-challenge-elm
Flux Challenge written in Elm
https://github.com/ravicious/flux-challenge-elm
Last synced: 3 months ago
JSON representation
Flux Challenge written in Elm
- Host: GitHub
- URL: https://github.com/ravicious/flux-challenge-elm
- Owner: ravicious
- License: mit
- Created: 2016-09-19T15:13:22.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2016-11-19T14:23:57.000Z (over 9 years ago)
- Last Synced: 2025-12-27T12:21:02.220Z (7 months ago)
- Language: Elm
- Homepage:
- Size: 21.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# flux-challenge-elm
Flux Challenge done in Elm
## Caveats
[flux-challenge readme](https://github.com/staltz/flux-challenge/blob/master/README.md) says the app
is supposed to cancel HTTP requests for jedis in some cases. In Elm, aborting a request is not
straightforward to accomplish. To work around that, flux-challenge-elm behavior differs from what's
specified in flux-challenge readme.
> Do not make any request for a sith that would be outside the list.
> Cancel any such obsolete request when the user scrolls.
Instead of canceling the requests, we don't add a jedi to the roster if it's not a master of
the first jedi or the apprentice of the last jedi.
> When either the current planet indicator changes OR loaded new rows: check if there is a displayed
> Dark Jedi whose home planet matches the current planet. If true, then display that Dark Jedi in
> red text, and cancel ALL ongoing HTTP requests for rows. Freeze the UI from scrolling until the
> current planet changes again and there is no red-highlighted Dark Jedi anymore.
Instead of canceling the ongoing requests, we don't add any new jedis to the roster when the UI
is frozen.