-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translation of docs/testing-components-with-graphql #202
Translation of docs/testing-components-with-graphql #202
Conversation
@@ -1,34 +1,18 @@ | |||
--- | |||
title: Testing Components with GraphQL | |||
title: GraphQLを用いたコンポーネントのテスト |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: GraphQLを用いたコンポーネントのテスト | |
title: GraphQL を用いたコンポーネントのテスト |
If you are using TypeScript this is a lot easier to get right as the type errors | ||
will tell you exactly what you should be passing to the components. This is why | ||
it is a good idea to define type interfaces for all of your GraphQL queries. | ||
もしあなたが Typescript を使用しているのならば、タイプエラーはあなたがコンポーネントに渡すべきなものについて正確に教えてくれるため、ずっと簡単にテストを行いやすくなります。これが、あなたの全ての GraphQL クエリーに対して、型のインターフェイスを定義することが良いアイデアとなる理由です。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
もしあなたが Typescript を使用しているのならば、タイプエラーはあなたがコンポーネントに渡すべきなものについて正確に教えてくれるため、ずっと簡単にテストを行いやすくなります。これが、あなたの全ての GraphQL クエリーに対して、型のインターフェイスを定義することが良いアイデアとなる理由です。 | |
もしあなたが TypeScript を使用しているのならば、タイプエラーはあなたがコンポーネントに渡すべきなものについて正確に教えてくれるため、ずっと簡単にテストを行いやすくなります。これが、あなたの全ての GraphQL クエリーに対して、型のインターフェイスを定義することが良いアイデアとなる理由です。 |
@@ -322,8 +270,6 @@ describe("Header", () => { | |||
}) | |||
``` | |||
|
|||
## Using TypeScript | |||
## Typescript を使った場合 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Typescript を使った場合 | |
## TypeScript を使った場合 |
I have added suggestions for fixing some minor typos. |
By the way, when committing a suggestion, you should commit using "Commit suggestion" or "Add suggestion to batch". Because the change belongs to the person who suggested it and should be clarified as the co-author of the commit. See the link below for more details. It's probably a hassle to get the exact email address of the person who suggested it, and GitHub has a feature that makes it easy, so you should use it. |
fix: add space Co-Authored-By: imbsky <git@bsky.moe>
Co-Authored-By: imbsky <git@bsky.moe>
@imbsky |
@@ -87,8 +65,8 @@ query IndexQuery { | |||
} | |||
``` | |||
|
|||
The output panel should now give you a nice JSON object with the query result. | |||
Here it is, trimmed to one node for brevity: | |||
出力結果は、クエリーの結果と共に、JSON オブジェクトをあなたに与えてくれます。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
改行を原文と合わせたいです。(Diffは二行になっていますが、Webサイトの方の最新と見比べています。)
68行目と69行目を同じ行にするようお願いします:bow:
Co-Authored-By: Jesse Katsumata <niconico.clarinet@gmail.com>
@Naturalclar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ありがとうございます!
Thanks @bebetaro for your contribution! |
概要
I translated
docs/testing-components-with-graphql
!Original Page here: https://www.gatsbyjs.org/docs/testing-components-with-graphql/
I really appreciate to your reviews! 🙇
I tried my best to translate, but if there are some mistakes in my translation, I will fix it asap!
Thanks!
チェックリスト
textlint
を使って校正を行いました。Allow edits from maintainers
にチェックを入れました。補足
Ref: #1