Learn-Queries.md #37

jonirrings · 2017-07-25T13:44:29Z

Signed-off-by: Jonir Rings peterpuyi@live.cn

close #10

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

ydfzgyj

内容之前已校对过，格式上

需要保留关键词的地方统一按照中文翻译（英文关键词）的格式。
链接之间增加空格
两处还需要再按新的格式规范修正一下

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

jonirrings · 2017-08-03T09:19:09Z

已修改，有劳复查

ydfzgyj · 2017-08-03T18:43:05Z

site/learn/Learn-Queries.md

 permalink: /learn/queries/
 next: /learn/schema/
-sublinks: Fields,Arguments,Aliases,Fragments,Variables,Operation Name,Directives,Mutations,Inline Fragments
+sublinks: 字段（Fields）,参数(Arguments),别名(Aliases),片段(Fragments),变量(Variables),操作名称(Operation Name),指令(Directives),变更(Mutations),内联片段(Inline Fragments)


后边的括号全是英文的

ydfzgyj · 2017-08-03T18:43:18Z

site/learn/Learn-Queries.md


 ```graphql
 # { "graphiql": true }
 {
  hero {
    name
-    # Queries can have comments!
+    # 查询可以有备注!


感叹号是英文的

ydfzgyj · 2017-08-03T18:44:09Z

site/learn/Learn-Queries.md


-> Oh, one more thing - the query above is *interactive*. That means you can change it as you like and see the new result. Try adding an `appearsIn` field to the `hero` object in the query, and see the new result.
+> 对了，还有一点 — 上述查询是*可交互的*。也就是你可以按你喜欢来改变查询，然后看看新的结果。尝试给查询中的 `hero` 对象添加一个` appearsIn` 字段，看看新的结果吧。


也是斜体改成粗体，这篇里的都是用的 * 啊……另一篇都是 _ 的

ydfzgyj · 2017-08-03T18:45:01Z

site/learn/Learn-Queries.md

@@ -72,15 +72,14 @@ In a system like REST, you can only pass a single set of arguments - the query p
 }
 ```

-Arguments can be of many different types. In the above example, we have used an Enumeration type, which represents one of a finite set of options (in this case, units of length, either `METER` or `FOOT`). GraphQL comes with a default set of types, but a GraphQL server can also declare its own custom types, as long as they can be serialized into your transport format.
+参数可以是多种不同的类型。上面例子中，我们使用了一个枚举类型，其代表了一个有限选项集合（本例中为长度单位，即是 `METER` 或者 `FOOT` ）。GraphQL 自带一套默认类型，但是GraphQL 服务器可以声明一套自己的定制类型，只要能序列化成你的传输格式即可。


FOOT 和括号之间不加空格，第二个 GraphQL 之前加空格

ydfzgyj · 2017-08-03T18:45:32Z

site/learn/Learn-Queries.md


+如果你眼睛够锐利，你可能已经发现，即便结果中的字段与查询中的字段能够匹配，但是因为他们并不包含参数，你就没法通过不同参数来查询相同字段。这便是为何你需要_别名_ — 这可以让你重命名结果中的字段为任意你想到的名字。


原来也有用下划线的……

我是按照原文换的啊……他用的md模版没细看，不知道有没区分_和单*。是翻译规范里面加了_和*转换规则么？

没加这个规则，只是吐槽原文也是乱用

ydfzgyj · 2017-08-03T18:47:48Z

site/learn/Learn-Queries.md


-In REST, any request might end up causing some side-effects on the server, but by convention it's suggested that one doesn't use `GET` requests to modify data. GraphQL is similar - technically any query could be implemented to cause a data write. However, it's useful to establish a convention that any operations that cause writes should be sent explicitly via a mutation.
+REST 中，任何请求都可能最后导致一些服务端副作用，但是约定上建议不要使用 `GET` 请求来修改数据。GraphQL 也是类似 — 技术上而言，任何查询都可以被实现为导致数据写入。然而，建一个约定来规范任何导致写入的操作都应该显示通过 变更（mutation）来发送。


看到一个错字，“显示”=>“显式”
另外变更前还是不要加空格吧

这个空格是漏网之鱼……

ydfzgyj · 2017-08-03T18:48:18Z

site/learn/Learn-Queries.md



-## Inline Fragments
+## 内联片段(Inline Fragments）


左括号是英文

ydfzgyj · 2017-08-03T18:48:52Z

site/learn/Learn-Queries.md



-### Meta fields
+### 元字段(Meta fields)


两个括号都是英文

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

jonirrings · 2017-08-04T02:18:07Z

已修正，有劳再次审校。

ydfzgyj · 2017-08-04T07:39:12Z

site/learn/Learn-Queries.md

@@ -4,7 +4,7 @@ layout: ../_core/DocsLayout
 category: 学习
 permalink: /learn/queries/
 next: /learn/schema/
-sublinks: 字段（Fields）,参数(Arguments),别名(Aliases),片段(Fragments),变量(Variables),操作名称(Operation Name),指令(Directives),变更(Mutations),内联片段(Inline Fragments)
+sublinks: 字段（Fields）,参数Arguments）,别名（Aliases）,片段（Fragments）,变量（Variables）,操作名称（Operation Name）,指令（Directives）,变更（Mutations）,内联片段（Inline Fragments）


参数后边掉了一个括号

ydfzgyj · 2017-08-04T07:39:59Z

site/learn/Learn-Queries.md


 ```graphql
 # { "graphiql": true }
 {
  human(id: "1000") {
    name
-    height(unit: FOOT)
+    height（unit: FOOT)


这个括号为什么要换成中文的？

ydfzgyj · 2017-08-04T07:41:01Z

site/learn/Learn-Queries.md


 某些情况下，你并不知道你将从 GraphQL 服务获得什么类型，这时候你就需要一些方法在客户端来决定如何处理这些数据。GraphQL 允许你在查询的任何位置请求 `__typename`，一个元字段，以获得那个位置的对象类型名称。

 ```graphql
 # { "graphiql": true}
 {
-  search(text: "an") {
+  search（text: "an") {


你是不是批量替换的😂

咦，看来替换多了。

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

jonirrings · 2017-08-04T08:04:10Z

已修正，有劳再次审校。喷血了:joy:，typo好多

ydfzgyj · 2017-08-04T16:58:27Z

site/learn/Learn-Queries.md

 permalink: /learn/queries/
 next: /learn/schema/
-sublinks: Fields,Arguments,Aliases,Fragments,Variables,Operation Name,Directives,Mutations,Inline Fragments
+sublinks: 字段（Fields）,参数Arguments）,别名（Aliases）,片段（Fragments）,变量（Variables）,操作名称（Operation Name）,指令（Directives）,变更（Mutations）,内联片段（Inline Fragments）


“参数”后边那个括号……为啥没加

😂，加上了。

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

jonirrings · 2017-08-05T04:34:19Z

@sqrthree 老大，这边有劳approve一下

linhe0x0 · 2017-08-05T04:43:45Z

site/learn/Learn-Queries.md


-In the previous example, we just asked for the name of our hero which returned a String, but fields can also refer to Objects. In that case, you can make a *sub-selection* of fields for that object. GraphQL queries can traverse related objects and their fields, letting clients fetch lots of related data in one request, instead of making several roundtrips as one would need in a classic REST architecture.
+在前一例子中，我们请求了我们主角的名字，返回了一个字符串类型（String），但是字段也能指代对象类型（Object）。这个时候，你可以对这个对象的字段进行 **次级选择（sub-selection）**。GraphQL 查询能够遍历相关对象及其字段，使得客户端可以一次请求查询大量相关数据，而不像传统 REST 架构中那样需要多次往返查询。


『次级选择』前面貌似多了个不必要的空格。

好的，在IDE上有自动换行，没注意到。:joy:

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

Learn-Queries.md translation done

d7e1240

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

linhe0x0 mentioned this pull request Jul 26, 2017

Learn-Queries.md #10

Closed

linhe0x0 added the 校对认领 label Jul 26, 2017

linhe0x0 self-requested a review July 26, 2017 07:35

linhe0x0 added the 正在校对 label Aug 1, 2017

ydfzgyj requested changes Aug 3, 2017

View reviewed changes

按照新格式规范修正“保留英文”和“链接前后的空格”

cf0db93

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

ydfzgyj requested changes Aug 3, 2017

View reviewed changes

按照新格式规范修正“英文斜体转换成中文粗体”，“保留英文的全角括号”，修正了破折号格式错误

b239b17

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

ydfzgyj requested changes Aug 4, 2017

View reviewed changes

替换部分错误的全角括号

ebd472d

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

ydfzgyj requested changes Aug 4, 2017

View reviewed changes

添加遗漏的左括号

a3573c4

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

linhe0x0 removed the 校对认领 label Aug 5, 2017

linhe0x0 reviewed Aug 5, 2017

View reviewed changes

去掉多于的空格

2daeeb3

Signed-off-by: Jonir Rings <peterpuyi@live.cn>

linhe0x0 approved these changes Aug 5, 2017

View reviewed changes

linhe0x0 merged commit 666e268 into xitu:zh-Hans Aug 5, 2017

linhe0x0 removed the 正在校对 label Aug 5, 2017

jonirrings deleted the Learn-Queries branch May 23, 2021 12:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Learn-Queries.md #37

Learn-Queries.md #37

jonirrings commented Jul 25, 2017 •

edited by linhe0x0

Loading

ydfzgyj left a comment

jonirrings commented Aug 3, 2017

ydfzgyj Aug 3, 2017

ydfzgyj Aug 3, 2017

ydfzgyj Aug 3, 2017

ydfzgyj Aug 3, 2017

ydfzgyj Aug 3, 2017

jonirrings Aug 4, 2017

ydfzgyj Aug 4, 2017

ydfzgyj Aug 3, 2017

jonirrings Aug 4, 2017

ydfzgyj Aug 3, 2017

ydfzgyj Aug 3, 2017

jonirrings commented Aug 4, 2017

ydfzgyj Aug 4, 2017

ydfzgyj Aug 4, 2017

ydfzgyj Aug 4, 2017

jonirrings Aug 4, 2017

jonirrings commented Aug 4, 2017

ydfzgyj Aug 4, 2017

jonirrings Aug 5, 2017 •

edited

Loading

jonirrings commented Aug 5, 2017

linhe0x0 Aug 5, 2017

jonirrings Aug 5, 2017


		> Oh, one more thing - the query above is interactive. That means you can change it as you like and see the new result. Try adding an `appearsIn` field to the `hero` object in the query, and see the new result.
		> 对了，还有一点 — 上述查询是可交互的。也就是你可以按你喜欢来改变查询，然后看看新的结果。尝试给查询中的 `hero` 对象添加一个` appearsIn` 字段，看看新的结果吧。


		如果你眼睛够锐利，你可能已经发现，即便结果中的字段与查询中的字段能够匹配，但是因为他们并不包含参数，你就没法通过不同参数来查询相同字段。这便是为何你需要_别名_ — 这可以让你重命名结果中的字段为任意你想到的名字。


		In REST, any request might end up causing some side-effects on the server, but by convention it's suggested that one doesn't use `GET` requests to modify data. GraphQL is similar - technically any query could be implemented to cause a data write. However, it's useful to establish a convention that any operations that cause writes should be sent explicitly via a mutation.
		REST 中，任何请求都可能最后导致一些服务端副作用，但是约定上建议不要使用 `GET` 请求来修改数据。GraphQL 也是类似 — 技术上而言，任何查询都可以被实现为导致数据写入。然而，建一个约定来规范任何导致写入的操作都应该显示通过变更（mutation）来发送。


		In the previous example, we just asked for the name of our hero which returned a String, but fields can also refer to Objects. In that case, you can make a sub-selection of fields for that object. GraphQL queries can traverse related objects and their fields, letting clients fetch lots of related data in one request, instead of making several roundtrips as one would need in a classic REST architecture.
		在前一例子中，我们请求了我们主角的名字，返回了一个字符串类型（String），但是字段也能指代对象类型（Object）。这个时候，你可以对这个对象的字段进行次级选择（sub-selection）。GraphQL 查询能够遍历相关对象及其字段，使得客户端可以一次请求查询大量相关数据，而不像传统 REST 架构中那样需要多次往返查询。

Learn-Queries.md #37

Learn-Queries.md #37

Conversation

jonirrings commented Jul 25, 2017 • edited by linhe0x0 Loading

ydfzgyj left a comment

Choose a reason for hiding this comment

jonirrings commented Aug 3, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jonirrings commented Aug 4, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jonirrings commented Aug 4, 2017

Choose a reason for hiding this comment

jonirrings Aug 5, 2017 • edited Loading

Choose a reason for hiding this comment

jonirrings commented Aug 5, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jonirrings commented Jul 25, 2017 •

edited by linhe0x0

Loading

jonirrings Aug 5, 2017 •

edited

Loading