Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CODE RUB: Foundation Correction #283

Merged
merged 1 commit into from
Jul 19, 2024
Merged

CODE RUB: Foundation Correction #283

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions 2. Services/2.1 Foundations/2.1 Foundations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ Foundation services should not integrate with more than one entity broker of any
### 2.1.2.2 Business Language

Broker-neighboring services speak primitive business language for their operations.
For instance, while a Broker may provide a method with the name `InsertStudentAsync` - the equivelant of that on the service layer would be `AddStudentAsync`.
For instance, while a Broker may provide a method with the name `InsertStudentAsync` - the equivalant of that on the service layer would be `AddStudentAsync`.

In general, most of the CRUD operations shall be converted from a storage language to a business language, and the same goes for non-storage operations such as Queues, for instance we say `PostQueueMessage` but on the business layer we shall say `EnqueueMessage`.

Expand Down Expand Up @@ -394,7 +394,7 @@ private void Validate(params (dynamic Rule, string Parameter)[] validations)
{
if(rule.Condition)
{
invalidStudentException.UpsertData(parameter, rule.Message);
invalidStudentException.UpsertDataList(parameter, rule.Message);
}
}

Expand Down
Loading