Ensure GraphQL query support for all front-end needs #43
Assignees
Comments
slifty
added a commit
that referenced
this issue
Mar 14, 2019
This follows the first few steps in the [Apollo Documentation](https://www.apollographql.com/docs/graphql-subscriptions/subscriptions-to-schema.html) for adding subscriptions to graphql. It sets up the schema to handle subscriptions and also creates the very initial integration with the PubSub implementation baked into the graphql-subscriptions library. As noted in that library, it is only appropriate for demos, not production. We will eventually want to replace it with a more robust PubSub implementation. Issue #44 Issue #43
slifty
added a commit
that referenced
this issue
Mar 14, 2019
This follows the first few steps in the [Apollo Documentation](https://www.apollographql.com/docs/graphql-subscriptions/subscriptions-to-schema.html) for adding subscriptions to graphql. It sets up the schema to handle subscriptions and also creates the very initial integration with the PubSub implementation baked into the graphql-subscriptions library. As noted in that library, it is only appropriate for demos, not production. We will eventually want to replace it with a more robust PubSub implementation. Issue #44 Issue #43
slifty
added a commit
that referenced
this issue
Mar 14, 2019
This follows the first few steps in the [Apollo Documentation](https://www.apollographql.com/docs/graphql-subscriptions/subscriptions-to-schema.html) for adding subscriptions to graphql. It sets up the schema to handle subscriptions and also creates the very initial integration with the PubSub implementation baked into the graphql-subscriptions library. As noted in that library, it is only appropriate for demos, not production. We will eventually want to replace it with a more robust PubSub implementation. Issue #44 Issue #43
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will be written in prose and pseudo-code, a genre known as English Major's Spec.
First, a representative example of one of the more common states of the interface. (To explore all states that will be discussed below, check out the interactive prototype.)
labelscounts, either as a raw series of timestamps, or as pre-summarized counts based on overall interval selected. (E.g., if the user is in "4 hour" view, we'd want a graph of entity appearance each… 30 minutes? 15 minutes? Whether the front-end arranged this by getting a list of each entity's timestamped appearance from the API, or a count summary for each x-axis interval, is up for discussion.)totalandrecentcan be done on the front-end.The text was updated successfully, but these errors were encountered: