Skip to content

Commit 1322809

Browse files
authored
Spelling/Grammar: Fixed typo
Fixed typo in dotnet build instructions
1 parent bea8467 commit 1322809

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The system is built with Docker in mind. However, it is possible to run and debu
1515
* git clone https://github.com/OPenPerpetuum/APIv2.git && cd APIv2/src
1616
* dotnet restore *optionally provide the "OpenPerpetuum.Api/OpenPerpetuum.Api.csproj" argument*
1717
* dotnet build OpenPerpetuum.Api/OpenPerpetuum.Api.csproj -c [Debug|Release] -o ./app
18-
* dotnet public OpenPerpetuum.Api/OpenPerpetuum.Api.csproj -c [Debug|Release] -o ./app
18+
* dotnet publish OpenPerpetuum.Api/OpenPerpetuum.Api.csproj -c [Debug|Release] -o ./app
1919
* <To start the app> cd app && dotnet OpenPerpetuum.Api.dll
2020

2121
# Installation (Windows)
@@ -84,4 +84,4 @@ When creating new objects with identifiers, ensure that the identifier is create
8484
There are some arguments for and against creating atomic commands/queries. How far down the rabbit hole do you go? As a general rule, anything that can be re-used should be its own unique command/query. It is also acceptible to composite commands and queries with additional queries.
8585

8686
**IMPORTANT**: When creating composite queries, *do not* include commands. It is vitally important that queries do not update the data-set state. Queries *must not* have the possibility of doing so and any requirement to call a command from a query should trigger you to re-think your local design.<br />
87-
On the flip-side, however, it is perfectly acceptible for Commands to utilise Queries, and other Commands. Compositing Commands within Commands I would *strongly* advise against. My main reasoning for this is that DNX does not support transactions as of yet. Compositing commands may give a false sense of security that those items will either all succeed, or all fail, and error handling may become excessive.
87+
On the flip-side, however, it is perfectly acceptible for Commands to utilise Queries, and other Commands. Compositing Commands within Commands I would *strongly* advise against. My main reasoning for this is that DNX does not support transactions as of yet. Compositing commands may give a false sense of security that those items will either all succeed, or all fail, and error handling may become excessive.

0 commit comments

Comments
 (0)