golang/ent
1
0
Fork 0
mirror of https://github.com/ent/ent.git synced 2026-05-24 09:31:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

ci: add spell checker and fix existing typo (#3420)

Browse Source 
* ci: add spell checker and fix existing typo

* chore: move typos.toml to .github

* fix: correct config file path
This commit is contained in:
Zhizhen He
2023-03-30 16:38:29 +08:00
committed by GitHub
parent e3cee0adc2
commit 6f847a3492
23 changed files with 59 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/md/tutorial-grpc-edges.md
View File

@@ -93,13 +93,13 @@ Observe the following changes:
* A new message, `Category` was created. This message has a field named `admin` corresponding to the `admin` edge on
the `Category` schema. It is a non-repeated field because we set the edge to be `.Unique()`. It's field number is `3`,
corresponding to the `entproto.Field` annotation on the edge definition.
* A new field `administered` was added to the `User` message definition. It is a `repeated` field, correspending to the
* A new field `administered` was added to the `User` message definition. It is a `repeated` field, corresponding to the
fact that we did not mark the edge as `Unique` in this direction. It's field number is `5`, corresponding to the
`entproto.Field` annotation on the edge.
### Creating Entities with their Edges
Let's demonstrate how to create an entity with it's edges by writing a test:
Let's demonstrate how to create an entity with its edges by writing a test:
```go
package main

4
doc/md/versioned-migrations.mdx
View File

@@ -678,7 +678,7 @@ Counter Initialization** header) and re-calculated on startup by looking at the
you happen to have a table with no rows yet, the autoincrement starting value is set to 0 for every table without any
entries. With the online migration feature this wasn't an issue, because the migration engine looked at the `ent_types`
tables and made sure to update the counter, if it wasn't set correctly. However, with versioned migration, this is no
longer the case. In oder to ensure, that everything is set up correctly after a server restart, make sure to call
longer the case. In order to ensure, that everything is set up correctly after a server restart, make sure to call
the `VerifyTableRange` method on the Atlas struct:
```go
@@ -862,7 +862,7 @@ generation, use the `schema.DisableChecksum()` option.
In addition to the usual `.sql` migration files the migration directory will contain the `atlas.sum` file. Every time
you let Ent generate a new migration file, this file is updated for you. However, every manual change made to the
mitration directory will render the migration directory and the `atlas.sum` file out-of-sync. With the Atlas CLI you can
migration directory will render the migration directory and the `atlas.sum` file out-of-sync. With the Atlas CLI you can
both check if the file and migration directory are in-sync, and fix it if not:
```shell