Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add basic layout and stub out components #44

Merged
merged 1 commit into from
Mar 7, 2019
Merged

Conversation

reefdog
Copy link
Contributor

@reefdog reefdog commented Mar 5, 2019

This is a very large commit that collates many smaller incremental commits and accomplishes the following:

  • Replaces prototype styling/layout with new styling/layout based on high-fidelity designs
  • Begins implementation of additional features and UX
  • Refactors components and adds new component stubs
  • Replaces separate stylesheet with styled-components

This is just the beginning.

Closes #30 and #31

@reefdog reefdog requested a review from slifty March 5, 2019 23:21
This is a very large commit that collates many smaller incremental commits and
accomplishes the following:

* Replaces prototype styling/layout with new styling/layout based on
  high-fidelity designs
* Begins implementation of additional features and UX
* Refactors components and adds new component stubs
* Replaces separate stylesheet with styled-components

This is just the beginning.

Closes #30 and #31
Copy link
Member

@slifty slifty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me!

Like we talked about by voice, we want to get this stuff merged in and we can go back and massage things like structure and format as we learn more about the Right Way To Do Things

@slifty slifty merged commit 3538b8c into master Mar 7, 2019
@slifty slifty deleted the 30-31-layout-and-stubs branch March 7, 2019 17:17
slifty added a commit that referenced this pull request 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 pull request 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 pull request 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 pull request Mar 14, 2019
Subscriptions are the goal, since they are likely much more efficient
and scale, but for the purposes of a demo we think that just using built
in polling functionality of ApolloClient will do the trick.

Issue #44
@slifty slifty mentioned this pull request Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants