File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed
website/src/pages/docs/data Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -218,7 +218,7 @@ class PostComponent {
218
218
219
219
constructor (private readonly apollo : Apollo ) {}
220
220
221
- upvote ({ postId , title }) {
221
+ changePostTitle ({ postId , title }) {
222
222
this .apollo
223
223
.mutate ({
224
224
mutation: CHANGE_POST_TITLE ,
@@ -238,9 +238,9 @@ class PostComponent {
238
238
```
239
239
240
240
For the example above, it is easy to construct an optimistic response, since we know the shape of
241
- the new comment and can approximately predict the created date . The optimistic response doesn't have
242
- to be exactly correct because it will always will be replaced with the real result from the server,
243
- but it should be close enough to make users feel like there is no delay.
241
+ the new post and can predict the new title . The optimistic response doesn't have to be exactly
242
+ correct because it will always be replaced with the real result from the server, but it should be
243
+ close enough to make users feel like there is no delay.
244
244
245
245
<Callout >
246
246
As this comment is * new* and not visible in the UI before the mutation, it won't appear
You can’t perform that action at this time.
0 commit comments