mirror of
https://github.com/ent/ent.git
synced 2026-05-24 09:31:56 +03:00
doc/md: fix some broken links (#2589)
This commit is contained in:
@@ -26,7 +26,7 @@ is to have an `ent` directory under the root directory of the project.
|
||||
|
||||
## Generate Assets
|
||||
|
||||
After adding a few [fields](schema-fields.md) and [edges](schema-edges.md), you want to generate
|
||||
After adding a few [fields](schema-fields.md) and [edges](schema-edges), you want to generate
|
||||
the assets for working with your entities. Run `ent generate` from the root directory of the project,
|
||||
or use `go generate`:
|
||||
|
||||
|
||||
@@ -70,4 +70,4 @@ If you are used to the definition of relations over edges, that's fine.
|
||||
The modeling is the same. You can model with `ent` whatever you can model
|
||||
with other traditional ORMs.
|
||||
There are many examples in this website that can help you get started
|
||||
in the [Edges](schema-edges.md) section.
|
||||
in the [Edges](schema-edges) section.
|
||||
|
||||
@@ -150,7 +150,7 @@ The full example exists in [GitHub](https://github.com/ent/ent/tree/master/examp
|
||||
|
||||
## Index On Edge Fields
|
||||
|
||||
Currently `Edges` columns are always added after `Fields` columns. However, some indexes require these columns to come first in order to achieve specific optimizations. You can work around this problem by making use of [Edge Fields](schema-edges.md#edge-field).
|
||||
Currently `Edges` columns are always added after `Fields` columns. However, some indexes require these columns to come first in order to achieve specific optimizations. You can work around this problem by making use of [Edge Fields](schema-edges#edge-field).
|
||||
|
||||
```go
|
||||
// Card holds the schema definition for the Card entity.
|
||||
|
||||
@@ -102,7 +102,7 @@ docker run --rm --name atlas-sum --detach --env MYSQL_ROOT_PASSWORD=pass --env M
|
||||
:::
|
||||
|
||||
The first step is to tell the migration engine to create and manage the `atlas.sum` by using the `schema.WithSumFile()`
|
||||
option. The below example uses an [instantiated Ent client](/docs/versioned-migrations.md#from-client) to generate new
|
||||
option. The below example uses an [instantiated Ent client](/docs/versioned-migrations#from-client) to generate new
|
||||
migration files:
|
||||
|
||||
```go
|
||||
|
||||
Reference in New Issue
Block a user