Skip to content

Commit

Permalink
linting (#64)
Browse files Browse the repository at this point in the history
* linting

* Update specification/src/tutorial/schema.md

---------

Co-authored-by: Phil Freeman <[email protected]>
  • Loading branch information
plcplc and paf31 authored Nov 14, 2023
1 parent ebfb47d commit cc036ae
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions specification/src/specification/queries/sorting.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ To compute the ordering from the `order_by` field, data connectors should implem
- For each [`OrderByElement`](../../reference/types.md#orderbyelement):
- If `element.target.type` is `column`, then to compare two rows, compare the value in the selected column. See type `column` below.
- If `element.target.type` is `star_count_aggregate`, compare two rows by comparing the row count of a related collection. See type `star_count_aggregate` below.
- If `element.target.type` is `single_count_aggregate`, compare two rows by comparing a single column aggregate. See type `single_count_aggregate` below.
- If `element.target.type` is `single_column_aggregate`, compare two rows by comparing a single column aggregate. See type `single_column_aggregate` below.

### Type `column`

Expand Down Expand Up @@ -53,9 +53,9 @@ For example, this query sorts article authors by their total article count:
{{#include ../../../../ndc-reference/tests/query/order_by_aggregate/request.json:3: }}
```

### Type `single_count_aggregate`
### Type `single_column_aggregate`

An ordering of type `single_count_aggregate` orders rows by an aggregate computed over rows in some [related collection](./relationships.md). If the respective aggregates are incomparable, the ordering should continue to the next [`OrderByElement`](../../reference/types.md#orderbyelement).
An ordering of type `single_column_aggregate` orders rows by an aggregate computed over rows in some [related collection](./relationships.md). If the respective aggregates are incomparable, the ordering should continue to the next [`OrderByElement`](../../reference/types.md#orderbyelement).

For example, this query sorts article authors by their maximum article ID:

Expand Down
4 changes: 2 additions & 2 deletions specification/src/specification/schema/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,5 +27,5 @@ See [`SchemaResponse`](../../reference/types.md#schemaresponse)
| `scalar_types` | [Scalar Types](scalar-types.md) |
| `object_types` | [Object Types](object-types.md) |
| `collections` | [Collection](collections.md) |
| `functions` | [Functions](Functions.md) |
| `procedures` | [Procedures](procedures.md) |
| `functions` | [Functions](functions.md) |
| `procedures` | [Procedures](procedures.md) |
2 changes: 1 addition & 1 deletion specification/src/tutorial/schema.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Schema

The [schema endpoint](../specification/schema/README.md) should return data describing the data connector's scalar and object types, along with any collections, functions and procedures which are exposed.
The schema endpoint should return data describing the data connector's scalar and object types, along with any collections, functions and procedures which are exposed.

```rust,no_run,noplayground
{{#include ../../../ndc-reference/bin/reference/main.rs:schema1}}
Expand Down

0 comments on commit cc036ae

Please sign in to comment.