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

Rehydrated reason for use #281

Closed
alexanderchan opened this issue Dec 5, 2018 · 13 comments
Closed

Rehydrated reason for use #281

alexanderchan opened this issue Dec 5, 2018 · 13 comments
Labels
amplify/js Issues tied to JS feature-request Request a new feature

Comments

@alexanderchan
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Was looking for a reason that Rehydrated is needed

Describe the solution you'd like
https://tylermcginnis.com/building-serverless-react-graphql-apps-with-aws-appsync/

Rehydrated will wait until the application cache has been read and is ready to use in the app before rendering the app. By default, this just shows some loading text, but this can be configured with our own UI like this if we would like:

https://hackernoon.com/aws-appsync-up-and-running-560a42d96ba7

Rehydrated is a helper from the aws-appsync-react library that will basically wait to render the application until the data is fetched from the API and the application is wired up with the AWSAppSyncClient

Describe alternatives you've considered
See links above

Additional context
Please include some text and an example of why and how to use.

@nikhil-dabhade
Copy link
Contributor

@alexanderchan Thank you for the feedback.
What documentation link were you following when you ran in to rehydrate?
Can you confirm if this is the one https://aws-amplify.github.io/docs/cli/graphql?sdk=js#tutorial-s3--react ?

@nikhil-dabhade
Copy link
Contributor

@alexanderchan : Sorry to bug you again. Can you confirm is the above was the only page where you ran in to Rehydrate ?

@alexanderchan
Copy link
Contributor Author

Hello, @nikhil-dabhade yes that's the only place I ran into Rehydrate. Thanks!

@nikhil-dabhade
Copy link
Contributor

@alexanderchan Thank you for confirming. I will circle back on the date to update this by next week.

@frankmuellr frankmuellr added the amplify/cli Issues tied to CLI label Jan 17, 2019
@kaustavghosh06 kaustavghosh06 added amplify/js Issues tied to JS and removed amplify/cli Issues tied to CLI labels Jun 6, 2019
@idanlo
Copy link

idanlo commented Jul 4, 2019

Any updates?

@stale
Copy link

stale bot commented Aug 3, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@idanlo
Copy link

idanlo commented Aug 3, 2019

not stale

@stale
Copy link

stale bot commented Sep 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@idanlo
Copy link

idanlo commented Sep 2, 2019

not stale

@cyrfer
Copy link

cyrfer commented Sep 25, 2019

I also do not understand why it is recommended. I removed it because it added a <div> and messed up my flexbox layout. I'm hopeful removing it won't mess up my client Subscriptions.

Mention of <Rehydrated> component is here:
https://github.com/awslabs/aws-mobile-appsync-sdk-js

There are some alternatives here:
awslabs/aws-mobile-appsync-sdk-js#448

@nagad814
Copy link

@nikhil-dabhade any update on this. As this currently breaking a production app.

@mauerbac
Copy link
Member

mauerbac commented Jun 8, 2020

In looking at the AppSync SDK issue, it seems to be merged. This issue should be resolved. Please open a new issue for further assistance.

@mauerbac mauerbac closed this as completed Jun 8, 2020
@aagamdoshi
Copy link

This issue isn't yet resolved, Kindly confirm, I faced the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amplify/js Issues tied to JS feature-request Request a new feature
Projects
None yet
Development

No branches or pull requests

10 participants