You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposed Fix:
Update the CLI command in the documentation to:
wgc subgraph create employees \
--namespace development \
--routing-url https://employees-api.fly.dev/graphql
Context:
These issues were encountered while following the official Cosmo Cloud Onboarding guide. They may cause unnecessary troubleshooting for first-time users trying to get the router and subgraphs working correctly. Addressing them would streamline onboarding and reduce confusion.
The text was updated successfully, but these errors were encountered:
raosudheesh
pushed a commit
to raosudheesh/cosmo-docs
that referenced
this issue
May 10, 2025
Description:
There are two minor issues in the Cosmo Cloud Onboarding documentation that can cause confusion for users trying to follow the guide.
Issues Identified:
1. Unexpected Redirect When Opening Playground:
In the section "Open the Playground", the instructions say:
However, clicking or navigating to http://localhost:3002 redirects the user to http://localhost:3002/graphql, which is incorrect as the playground will be running at http://localhost:3002.
Proposed Fix:
Update the redirect URL path to http://localhost:3002
2. Incorrect Routing URL in Subgraph Creation:
In the Employee section of the guide, the following command is shown:
The URL https://employee-api.fly.dev/graphql is invalid or unreachable.
Correct URL:
It should be: https://employees-api.fly.dev/graphql (with a plural employees).
Proposed Fix:
Update the CLI command in the documentation to:
Context:
These issues were encountered while following the official Cosmo Cloud Onboarding guide. They may cause unnecessary troubleshooting for first-time users trying to get the router and subgraphs working correctly. Addressing them would streamline onboarding and reduce confusion.
The text was updated successfully, but these errors were encountered: