Use flask-login instead of client-side sessions for storing selected location and orders

frontend/Calculator.elm

@@ -9,15 +9,7 @@ import Select
 
 type Tax = Net | Gross
 
--- Duplicated from Entry.elm but too lazy to sandwich this out
+ctShow ct = case ct of
-type alias TaxGroup =
-  { id : Int
-  , description : String
-  , percentage : Float
-  }
-
-showTax : Tax -> String
-showTax tax = case tax of
   Gross -> "Brutto"
   Net -> "Netto"
 
@@ -27,13 +19,11 @@ type alias Model =
   , bundleSize : NumberInput.Model Int
   }
 
-init : Float -> Model
 init bundlePrice = Model
-  (Select.init showTax showTax Net [Net, Gross])
+  (Select.init ctShow ctShow Net [Net, Gross])
   (NumberInput.fromFloat bundlePrice)
   (NumberInput.fromInt 1)
 
-getResult : Model -> TaxGroup -> Maybe Float
 getResult model taxGroup =
   case (NumberInput.get model.bundlePrice, NumberInput.get model.bundleSize) of
     (Just bundlePrice, Just bundleSize) ->
@@ -51,7 +41,6 @@ type Msg
   | SetBundlePrice String
   | SetBundleSize String
 
-update : Msg -> Model -> Model
 update msg model = case msg of
   SetTax key ->
     { model | tax = Select.update key model.tax }
@@ -60,7 +49,6 @@ update msg model = case msg of
   SetBundleSize str ->
     { model | bundleSize = NumberInput.update str model.bundleSize }
 
-view : Model -> TaxGroup -> Html Msg
 view model taxGroup =
   let
     mainPart =
@@ -124,5 +112,4 @@ view model taxGroup =
         ]
       ]
 
-roundTo : Int -> Float -> Float
+roundTo places x = toFloat (round <| x * 10 ^ places) / 10 ^ places
-roundTo places x = toFloat (round <| x * 10 ^ toFloat places) / 10 ^ toFloat places

frontend/Entry.elm

@@ -14,50 +14,6 @@ import Calculator
 import NumberInput
 import Select
 
-{-
-Elm forces us to use the Elm architecture:
-
-              ┌──────┐
- ┌─────Model──► view ├──Html───────┐
- │            └──────┘             │
- │                                 │
-┌┴─────────────────────────────────▼┐
-│            Elm runtime            │
-└▲─────────────────────────────────┬┘
- │                                 │
- │            ┌──────┐             │
- └─Model+Cmd──┤update◄──Msg+Model──┘
-              └──────┘
-
-This architecture is similar to what React does but its implementation
-in Elm is a bit special since it's purely functional and side effects
-are isolated into the runtime system.
-
-An Elm component is usually centered around two types, Model and Msg.
-Model contains all data the application is concerned with, including the state
-of UI elements. Msg encodes all updates to Model that the application supports.
-
-In addition to Msg and Model, we have to provide two functions, view and update.
-
-view : Model -> Html Msg
-update : Msg -> Model -> (Model, Cmd Msg)
-
-view maps a Model to a DOM tree. Events in this DOM tree create Msg values.
-update maps a Msg and a Model to a new Model. In addition, update can create
-a command. Commands are used to make the runtime do side effects, which in
-turn create new Msg values.
-
-For example, we have a SetSearchTerm message which simply updates the searchTerm
-property in the model. This message is triggered every time the search box input
-is changed. Submitting the search box form triggers a SubmitSearch event.
-This event leaves the model unchanged but issues a command that sends the search
-term to a JSON endpoint. When the request successfully resolves, the runtime
-triggers a ReceiveSearchResults messages which updates the list of search results
-in the model.
-
-See Calculator.elm for a simpler example of this architecture.
--}
-
 main = Browser.element
   { init = \globals ->
     ( Context globals <| ItemSearch { searchTerm = "", searchResults = [] }