Skip to content

Commit 5731880

Browse files
committed
Update README.md
1 parent ba4626b commit 5731880

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Replace `<ConnectionString>` with a valid database connection string.
4040

4141
### Generation Output
4242

43-
The `generate` command will create the follow files and directory structure by default. The root directory defaults to the current working directory. Most of the output names and locations can be customized in the [configuration file](https://efg.loresoft.com/en/latest/configuration/)
43+
The `generate` command will create the follow files and directory structure by default. The root directory defaults to the current working directory. Most of the output names and locations can be customized in the [configuration file](https://efg.loresoft.com/configuration/)
4444

4545
#### Data Context Output
4646

@@ -56,7 +56,7 @@ The mapping directory contains a fluent mapping class to map each entity to its
5656

5757
## Initialize Command
5858

59-
The `initialize` command is used to create the configuration yaml file and optionally set the [connection string](https://efg.loresoft.com/en/latest/connectionString/). The configuration file has many options to configure the generated output. See the [configuration file](https://efg.loresoft.com/en/latest/configuration/) documentation for more details.
59+
The `initialize` command is used to create the configuration yaml file and optionally set the [connection string](https://efg.loresoft.com/connectionString/). The configuration file has many options to configure the generated output. See the [configuration file](https://efg.loresoft.com/configuration/) documentation for more details.
6060

6161
The following command will create an initial `generation.yaml` configuration file as well as setting a user secret to store the connection string.
6262

@@ -129,7 +129,7 @@ Entity Framework Core Generator supports the following databases.
129129
- MySQL
130130
- Sqlite
131131

132-
The provider can be set via command line or via the [configuration file](https://efg.loresoft.com/en/latest/configuration/).
132+
The provider can be set via command line or via the [configuration file](https://efg.loresoft.com/configuration/).
133133

134134
Set via command line
135135

@@ -151,7 +151,7 @@ The database schema is loaded from the metadata model factory implementation of
151151

152152
## View Models
153153

154-
Entity Framework Core Generator supports generating [Read](https://efg.loresoft.com/en/latest/md/read/), [Create](https://efg.loresoft.com/en/latest/md/create/) and [Update](https://efg.loresoft.com/en/latest/md/update/) view models from an entity. Many projects rely on view models to shape data. The model templates can be used to quickly get the basic view models created. The model templates also support regeneration so any database change can easily be sync'd to the view models.
154+
Entity Framework Core Generator supports generating [Read](https://efg.loresoft.com/md/read/), [Create](https://efg.loresoft.com/md/create/) and [Update](https://efg.loresoft.com/md/update/) view models from an entity. Many projects rely on view models to shape data. The model templates can be used to quickly get the basic view models created. The model templates also support regeneration so any database change can easily be sync'd to the view models.
155155

156156
## Change Log
157157

0 commit comments

Comments
 (0)