mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-10-26 10:20:54 +03:00
fix spelling and grammar in docs (#709)
This commit is contained in:
parent
92c8ec55b2
commit
fade5b39f8
@ -3,7 +3,7 @@
|
||||
Hasura CLI: hasura completion
|
||||
-----------------------------
|
||||
|
||||
Generate auto completion code
|
||||
Generate auto-completion code
|
||||
|
||||
Synopsis
|
||||
~~~~~~~~
|
||||
|
@ -9,7 +9,7 @@ Synopsis
|
||||
~~~~~~~~
|
||||
|
||||
|
||||
Browser based login to access your clusters and other information from hasura.io dashboard.
|
||||
Browser-based login to access your clusters and other information from hasura.io dashboard.
|
||||
|
||||
::
|
||||
|
||||
|
@ -124,7 +124,7 @@ in the ``migrations/`` directory in your project.
|
||||
|
||||
.. note::
|
||||
|
||||
Migrations are only created when using the Console though CLI.
|
||||
Migrations are only created when using the Console through CLI.
|
||||
|
||||
Step 6: Apply the migrations to another instance of the GraphQL engine
|
||||
----------------------------------------------------------------------
|
||||
|
@ -103,7 +103,7 @@ Using jsonb operators
|
||||
Update using **_append** operator
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Update any ``jsonb`` column by appending it with given value. Since it is a json value, it should
|
||||
provided through a variable.
|
||||
be provided through a variable.
|
||||
|
||||
Append the ``extra_info`` of an article:
|
||||
|
||||
@ -230,7 +230,7 @@ Delete the key ``key3`` in the ``extra_info`` of an article:
|
||||
|
||||
Update using **_delete_elem** operator
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Update any ``jsonb`` column by deleting a array element with given index value. Input value should be a ``Int``.
|
||||
Update any ``jsonb`` column by deleting an array element with given index value. Input value should be a ``Int``.
|
||||
|
||||
Delete the element at ``2`` in ``jsonb`` array ``["a", "b", "c"]`` of column ``extra_info`` of an article:
|
||||
|
||||
|
@ -2,7 +2,7 @@ Upsert mutation
|
||||
===============
|
||||
|
||||
To convert an **insert** mutation into an **upsert** one, you need to specify the unique or primary key constraint(s) and the
|
||||
columns to be updated in the case of a conflict or violation. You can specify a constraint using the ``constriant`` argument and
|
||||
columns to be updated in the case of a conflict or violation. You can specify a constraint using the ``constraint`` argument and
|
||||
update columns using the ``update_columns`` argument.
|
||||
|
||||
.. note::
|
||||
@ -102,8 +102,8 @@ is the set of columns that is updated. For example, if your query as follows:
|
||||
}
|
||||
|
||||
The column ``"is_premium"`` for the ``"Jack"`` row is set to its ``DEFAULT`` value because the union of all columns across objects
|
||||
is ``{name, email_sent, is_premium}``. However ou can explicitly control the columns that are updated on conflict using
|
||||
``update_columns`` as specified in following section.
|
||||
is ``{name, email_sent, is_premium}``. However, you can explicitly control the columns that are updated on conflict using
|
||||
``update_columns`` as specified in the following section.
|
||||
|
||||
With non empty "update_columns"
|
||||
-------------------------------
|
||||
|
@ -1,6 +1,6 @@
|
||||
Using multiple arguments in a query
|
||||
===================================
|
||||
Multiple arguments can be used together in the same query. For example, if you want to use the ``where`` argument to
|
||||
Multiple arguments can be used together in the same query. For example, you can use the ``where`` argument to
|
||||
filter the results and then use the ``order_by`` argument to sort them.
|
||||
|
||||
For example, fetch a list of authors and only 2 of their published articles that are sorted by their date of publication:
|
||||
|
@ -9,7 +9,7 @@ Query using an array relationship
|
||||
The following is an example of a nested object query using the ``array relationship`` between an author and
|
||||
articles.
|
||||
|
||||
Fetch a list of authors and a nested list of the each author’s articles:
|
||||
Fetch a list of authors and a nested list of each author’s articles:
|
||||
|
||||
.. graphiql::
|
||||
:view_only:
|
||||
|
@ -94,7 +94,7 @@ Fetch 5 authors from the list of all authors, starting with the 6th one:
|
||||
|
||||
Limit results in a nested object
|
||||
--------------------------------
|
||||
Fetch a list of authors and a list of 2 of each of their rticles:
|
||||
Fetch a list of authors and a list of 2 of each of their articles:
|
||||
|
||||
.. graphiql::
|
||||
:view_only:
|
||||
@ -173,4 +173,4 @@ Fetch a list of authors and a list of 2 of each of their rticles:
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -20,7 +20,7 @@ For example, fetch data for an author whose name is "Sidney":
|
||||
}
|
||||
|
||||
You can also use the nested ``articles`` object to filter rows from the ``author`` table. This query fetches a list of
|
||||
authors who have articles with rating greater than 4:
|
||||
authors who have articles with a rating greater than 4:
|
||||
|
||||
.. code-block:: graphql
|
||||
:emphasize-lines: 3
|
||||
@ -619,4 +619,4 @@ Fetch a list of articles rated more than 4 or published after "01/01/2018":
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -12,7 +12,7 @@ GraphQL schema:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
# If the GraphQL engine is running at at https://my-graphql-engine.com/v1alpha1/graphql,
|
||||
# If the GraphQL engine is running at https://my-graphql-engine.com/v1alpha1/graphql,
|
||||
# without an access key
|
||||
gq https://my-graphql-engine.com/v1alpha1/graphql --introspect > schema.graphql
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user