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
-_tRPC_: Swell includes full support for all methods of TypeScript Remote Procedure Calls including batch call support for queries and mutations as well as subscription
Calls are currently being made using by using http get and post request using TRPC's http RPC specification (See [RPC docs](https://trpc.io/docs/rpc)). TLDR- inputs for query procedures will be turn into uri-encoded json string and send as query param while inputs for mutate procedures will be store inside of the body.
53
+
54
+
Batch requests can be made by adding multiple procedures before sending out the request, all query procedures will get batch together into one singular get request and all mutate procedures will get batch together into one singular put request, if there are mixture of query and mutate procedures call in one request, the app will send out both a post and get request concurrently and combine the response into one response.
55
+
56
+
Nested endpoint must follow the general format parentEndpoint.childEndpoint.grandchildEndpoint. For example:
A request to the above endpoint must have the mutate option selected from the drop down menu, must have an endpoint of .user.update and a input body of {"userId": "1","name": "Luke"}
63
+
64
+
See [tRPC docs](https://trpc.io/docs/) for more information on sending tRPC requests or setting up a tRPC server.
65
+
48
66
## Additional features
49
67
50
68
-_Stress testing for HTTP/2 and GraphQL_: Test your server backend with Swell's stress testing feature to ensure your server can manage expected and unexpected loads accordingly
@@ -70,20 +88,6 @@ Swell is a one-stop shop for sending and monitoring your API requests:
70
88
-_Mock Server_: Swell allows you to create your own HTTP/2 mock server to facilitate front-end development without depending on a fully built backend server.
Calls are currently being made using Swell's own TRPCProxyClient generated from the URL provided by the user.
78
-
Batch requests must be entered one request per line. Swell will treat each line of code entered into the editor as a separate request before batching and returning responses.
79
-
Each request must follow the general format client.procedure.querytype(). For example:
80
-
81
-
```js
82
-
client.getUser.query({ name:'Luke Skywalker' });
83
-
```
84
-
85
-
See [tRPC docs](https://trpc.io/docs/) for more information on sending tRPC requests or setting up a tRPC server.
86
-
87
91
-_Webhooks_: Swell includes user-defined HTTP callback connection testing designed to test other server's connection to the web and ability to send data. The test insures that when an event occurs, the source site makes an HTTP request to the URL configured for the webhook.
Copy file name to clipboardExpand all lines: docs/DEV-README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,7 @@ From a functionality standpoint:
66
66
- Consistent UI/UX styling and color palette
67
67
- Make requests via HTTP/2
68
68
- Query, Mutation, Subscribe/unsubscribe to GraphQL endpoints
69
+
- Query, Mutation, Subscribe/unsubscribe to tRPC endpoints
69
70
- HTTP/2 stress testing with `GET` requests
70
71
- GraphQL stress testing with `Query`
71
72
- Mock server for HTTP/2 (`Express`)
@@ -110,7 +111,8 @@ For the following technologies - if you reference the gifs in `readme` and try t
110
111
111
112
<!-- - gRPC -->
112
113
113
-
- tRPC
114
+
<!-- - tRPC -->
115
+
114
116
- OpenAPI
115
117
116
118
If future groups have a desire to iteration on the above features, please ensure the basic functionality works as expected, update E2E testing in `./test/testSuite.js` before adding new features.
@@ -161,7 +163,7 @@ Continuous Integration has been implemented using GitHub Actions. If you would l
161
163
- Make any necessary adjustments to the workflow and continue testing it on ci-draft and ci-main until the workflow is functioning as intended
162
164
- Finally, open a pull request to merge the new workflow into the dev and/or main branches
163
165
164
-
The idea is to troubleshoot new workflows before applying them to the dev or main branches.
166
+
The idea is to troubleshoot new workflows before applying them to the dev or main branches.
165
167
166
168
A Continuous Deployment pipeline would be an advantageous addition, as its absence blocks the ability to automatically package and release new iterations of the application. The groundwork for it is there (see the “scripts” and “build” properties in package.json) but packaging for Linux will need some attention, as outlined in the next section.
0 commit comments