Update for Elm 0.19

.travis.yml

@@ -2,38 +2,23 @@ sudo: false
 
 language: node_js
 node_js:
-  "9.11.1"
+  "lts/*"
 
 cache:
   directories:
     - test/elm-stuff/build-artifacts
-    - sysconfcpus
     - node_modules
 
 os:
   - linux
 
 env:
   matrix:
-    - ELM_VERSION=0.18.0
-
-before_install:
-  - npm i -g npm@^5.6.0
-  - npm --version
-  - |
-    # CI build time workaound
-    # https://github.com/elm-lang/elm-compiler/issues/1473#issuecomment-245704142
-    if [ ! -d $TRAVIS_BUILD_DIR/sysconfcpus/bin ]; then
-      git clone https://github.com/obmarg/libsysconfcpus.git
-      cd libsysconfcpus
-      ./configure --prefix=$TRAVIS_BUILD_DIR/sysconfcpus
-      make && make install
-    fi
+    - ELM_VERSION=0.19.0
 
 install:
-  - export PATH="$TRAVIS_BUILD_DIR/sysconfcpus/bin:$PATH"
   - npm install
 
 script:
-  - sysconfcpus -n 2 npm test
-  - sysconfcpus -n 2 npm run approve
+  - npm test
+  - npm run approve

CHANGELOG-ELM-PACKAGE.md

@@ -11,6 +11,24 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [1.0.0] - 2018-08-22
 
+### Removed
+
+- **Subscriptions Low-Level Data-Transfer Layer** As before, this library will
+  generate code based on the subscriptions defined in your GraphQL schema.
+  And you will be able to use `Graphql.Document.serializeSubscription` to
+  get a `String` that you can send over to your server when you open a subscription.
+  Then you'll be able to use the `Graphql.Document.decoder` from your subscription
+  to decode the JSON responses from the server.
+  What's been removed is just the low level protocols for doing the websocket connection.
+  As per [this issue](https://github.com/dillonkearns/elm-graphql/issues/43),
+  this responsibility will be moved out of the core `dillonkearns/elm-graphql`
+  package in order to decouple this library from the low-level details which
+  differ between different GraphQL server implementations.
+
+The low-level data transfer logic for connecting over websockets to a subscription
+has been removed from this package.
+https://github.com/dillonkearns/elm-graphql/issues/43
+
 ### Changed
 
 - Rename package from `dillonkearns/graphqelm` to `dillonkearns/elm-graphql`

README.md

@@ -4,6 +4,8 @@
 
 [![Build Status](https://travis-ci.org/dillonkearns/elm-graphql.svg?branch=master)](https://travis-ci.org/dillonkearns/elm-graphql)
 
+(Formerly Graphqelm, [read about why the name changed.](https://github.com/dillonkearns/elm-graphql/issues/23))
+
 Why use this package over the other available Elm GraphQL packages? This is the only one that
 generates type-safe code for your entire schema. (It's also the only type-safe
 library with Elm 0.18 support, see
@@ -132,10 +134,21 @@ All core features are supported. That is, you can build any query or mutation
 with your `dillonkearns/elm-graphql`-generated code, and it is guaranteed to be valid according
 to your server's schema.
 
-I am currently experimenting with subscriptions, checkout
-[this live demo](https://rebrand.ly/graphqelm-subscriptions) or
-[`examples/src/Subscription.elm`](https://github.com/dillonkearns/elm-graphql/blob/master/examples/src/Subscription.elm)
-for an example using Phoenix/Absinthe as a backend.
+`dillonkearns/elm-graphql` will generate code for you to generate subscriptions
+and decode the responses, but it doesn't deal with the low-level details for
+how to send them over web sockets. To do that, you will need to use
+custom code or a package that knows how to communicate over websockets (or whichever
+protocol) to setup a subscription with your particular framework. See
+[this discussion](https://github.com/dillonkearns/elm-graphql/issues/43) for why
+those details are not handled by this library directly.
+
+I would love to hear feedback if you are using GraphQL Subscriptions. In particular,
+I'd love to see live code examples to drive any improvements to the Subscriptions
+design. Please ping me on Slack, drop a message in the
+[#graphql](https://elmlang.slack.com/channels/graphql) channel, or open up a
+Github issue to discuss!
+
+[this live demo](https://rebrand.ly/graphqelm-subscriptions).
 
 I would like to investigate generating helpers to make pagination simpler
 for Connections (based on the