Merge branch 'static-http'

.travis.yml

@@ -8,11 +8,11 @@ os:
 
 env:
   matrix:
-    - ELM_VERSION=0.19.0
+    - ELM_VERSION=0.19.1
 
 before_install:
   - npm i -g npm@lts
-  - npm i -g elm@0.19.0-no-deps
+  - npm i -g elm@latest-0.19.1
   - npm i -g npm@6.4.1
 
 install:

CHANGELOG-ELM.md

@@ -9,6 +9,20 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+### Added
+- The generated `Pages.elm` module now includes `builtAt : Time.Posix`. Make sure you have `elm/time` as a dependency in your project!
+   You can use this when you make API requests to filter based on a date range starting with the current date.
+   If you want a random seed that changes on each build (or every week, or every month, etc.), then you can use this time stamp
+   (and perform modulo arithemtic based on the date for each week, month, etc.) and use that number as a random seed.
+
+### Changed
+- Instead of initializing an application using `Pages.application` from the generated `Pages` module, you now initialize the app
+    using `Pages.Platform.application` which is part of the published Elm package. So now it's easier to browse the docs.
+    You pass in some internal data from the generated `Pages.elm` module now by including
+    this in the application config record:  `Pages.Platform.application { internals = Pages.internals, ... <other fields> }`.
+- Add init argument and user Msg for initial PagePath and page changes (see [#4](https://github.com/dillonkearns/elm-pages/issues/4)).
+
+
 ## [1.0.1] - 2019-11-04
 
 ### Fixed

CHANGELOG-NPM.md

@@ -29,3 +29,9 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 ### Fixed
 - Use hidden `<div>` to listen for Elm view renders instead of wrapping entire
    page in an extra div. Fixes [#5](https://github.com/dillonkearns/elm-pages/issues/5).
+
+### Changed
+- Add `onPageChange : PagePath Pages.PathKey -> userMsg` field to `Pages.application` config record.
+    This is analagous to `onUrlChange` in `Browser.application`, except that you get a
+    type-safe `PagePath Pages.PathKey` because it is guaranteed that you will only
+    go to one of your static routes when this `Msg` is fired. Fixes [#4](https://github.com/dillonkearns/elm-pages/issues/4).