forked from dyne/zenpub-client
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Migration to Bonfire #167
Labels
bonfire-migration
Issues linked to ZenPub to Bonfire migration
Comments
Note the documentation exception in that the API Tour page is not yet updated. |
@adam-burns I updated the issue accordingly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Legacy migration work Asses ZenPub replacement with BonFire #121 Most of the issues here are solved.
Bonfire public instance for development is here https://reflow-demo.dyne.org/api/graphql and documentation available https://reflow-demo.dyne.org/api/explore. Also, the main documentation in reflowos.dyne.org is updated except for the API Tour page.
Changing remote server: In the
.env
file replaceREACT_APP_GRAPHQL_ENDPOINT=https://api.reflowproject.eu/api/graphql
(ZenPub) byREACT_APP_GRAPHQL_ENDPOINT=https://reflow-demo.dyne.org/api/graphql
(Bonfire) and runyarn start
.Almost all the existing
queries
andmutations
are now implemented in the new Bonfire. See issue WeLoop: Sufficient Social GraphQL exposure for initial use cases dyne/reflow-os#18 (comment)However some minor changes are required. Preliminary list:
anonLogin
now replaced bylogin
. See docstrack
andtrace
previously return onlyeconomicResouce
now can return multiple types andeconomicResource
type needs to be detected before it's casted. See:The text was updated successfully, but these errors were encountered: