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
fix(docs): update README and development documentation for v2 endpoints
- Updated GraphQL endpoint references from v1 to v2 in README and development documentation.
- Adjusted API routes in various controllers to reflect the new v2 structure.
- Added new response types in schema.graphql for hyperboard and section entries.
- Updated test descriptions to align with the new v2 endpoints.
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,10 @@ The API implements a fallback to the first available RPC. You can set the RPCs i
28
28
29
29
### Supabase
30
30
31
-
* Install Docker
32
-
*`git submodule init`
33
-
*`git submodule update --remote`
34
-
*`pnpm supabase:start:all`
31
+
- Install Docker
32
+
-`git submodule init`
33
+
-`git submodule update --remote`
34
+
-`pnpm supabase:start:all`
35
35
36
36
This will spin up 2 Supabase instances in Docker, one for the indexer service (caching) and one for the data service (static data) which are both exposed by the API.
37
37
@@ -43,21 +43,21 @@ From both instances, you can get their respective keys and add them to the env v
43
43
44
44
This will run a live production instance by running `swc` to compile the code and `nodemon` to restart the server on changes.
45
45
46
-
You can then find the API at `localhost:4000/spec` (Swagger instance) and the GraphQL at `localhost:4000/v1/graphql`
46
+
You can then find the API at `localhost:4000/spec` (Swagger instance) and the GraphQL at `localhost:4000/v2/graphql`
47
47
48
48
## Deployments
49
49
50
50
Production: `https://api.hypercerts.org/`
51
51
Staging: `https://staging-api.hypercerts.org`
52
52
53
53
`/spec` - Swagger instance documenting the API and exposing a playground to experiment with the endpoints
54
-
`/v1/graphql` - GraphQL API to access hypercerts data like claims, fractions, attestations, allow lists
54
+
`/v2/graphql` - GraphQL API to access hypercerts data like claims, fractions, attestations, allow lists
55
55
56
56
## Scripts
57
57
58
58
-`dev`: Starts the development server using `nodemon`, which will automatically restart the server whenever you save a file that the server uses.
59
59
-`build`: Denerates the OpenAPI specification and routes using `tsoa`, and then compiles the TypeScript code into JavaScript using `swc`. The compiled code is output to the `dist` directory.
60
-
-`start`: Starts the application in production mode.
60
+
-`start`: Starts the application in production mode.
61
61
-`lint`: Runs `eslint` on the codebase to check for linting errors.
62
62
-`test`: Runs tests using `vitest`
63
63
@@ -86,38 +86,38 @@ The API also provides an upload and validation endpoint for hypercert and allow
86
86
graph TB
87
87
Client[Client Applications]
88
88
API[Hypercerts API :4000]
89
-
89
+
90
90
subgraph "API Endpoints"
91
91
Swagger["/spec\nSwagger Documentation"]
92
-
GraphQL["/v1/graphql\nGraphQL Endpoint"]
92
+
GraphQL["/v2/graphql\nGraphQL Endpoint"]
93
93
Upload["Upload & Validation\nEndpoints"]
94
94
end
95
-
95
+
96
96
subgraph "Data Services"
97
97
Static[("Static Data Service\n(Supabase DB)\n- User Data\n- Collections\n- Signed Orders")]
0 commit comments