From 41a7cb42c192b57012bcd8ea318594a8c4216330 Mon Sep 17 00:00:00 2001 From: DJ Adams Date: Tue, 19 Nov 2024 08:54:03 +0000 Subject: [PATCH] Super minor typo fixes for new Aspect-oriented Modelling section --- cds/aspects.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/cds/aspects.md b/cds/aspects.md index a93828fc3..9d25478f8 100644 --- a/cds/aspects.md +++ b/cds/aspects.md @@ -8,7 +8,7 @@ status: released The technique of [*Aspects*](cdl#aspects) provides very powerful means to organize your models in a way that keeps your core domain models concise and comprehensible by factoring out secondary concerns into separate files, defining and reusing common aspects, as well as adapting reused definitions to specific needs. -**See also:** Respective section in [*Five reasons to use CAP*](https://qmacro.org/blog/posts/2024/11/07/five-reasons-to-use-cap/) , and [*Separating concerns and focusing on important stuff*](https://qmacro.org/blog/posts/2024/11/04/separating-concerns-and-focusing-on-the-important-stuff/) blogs by DJ Adams. {.learn-more} +**See also:** Respective section in [*Five reasons to use CAP*](https://qmacro.org/blog/posts/2024/11/07/five-reasons-to-use-cap/) , and [*Separating concerns and focusing on important stuff*](https://qmacro.org/blog/posts/2024/11/04/separating-concerns-and-focusing-on-the-important-stuff/) blog posts by DJ Adams. {.learn-more} @@ -146,7 +146,7 @@ annotate CatalogService.Books with @UI:{ -Quite frequently, you want some common aspects be factored out and shared by and applied to multiple entities. For example, lets assume we'd want to factor out the common aspects of a standardized primary key, managed data, change tracking, extensibility, and temporal data... +Quite frequently, you want some common aspects factored out and shared by and applied to multiple entities. For example, lets assume we'd want to factor out the common aspects of a standardized primary key, managed data, change tracking, extensibility, and temporal data... @@ -268,7 +268,7 @@ entity Bar : cuid, managed, temporal {...} ::: tip Advantages of that approach -Not only does that approach allow clearer separation of concerns, and thus freedom of choice which combinations of aspects to pick for consumers, it also allows distributed ownership of such reuse aspects, as they don't depend on each others. +Not only does that approach allow clearer separation of concerns, and thus freedom of choice which combinations of aspects to pick for consumers, it also allows distributed ownership of such reuse aspects, as they don't depend on each other. ::: @@ -334,7 +334,7 @@ extend managed with { ### Adding Reuse Aspects -And as the `:` notation to *inherit* an aspect is essentially just [syntactical sugar](cdl#includes) to extending a given definition with a [*named* aspect](cdl#named-aspects), you can also adapt a reused definition to *inherit* from a common reuse aspect from 'the outside' like so: +And as the `:` notation to *inherit* an aspect is essentially just [syntactical sugar](cdl#includes) for extending a given definition with a [*named* aspect](cdl#named-aspects), you can also adapt a reused definition to *inherit* from a common reuse aspect from 'the outside' like so: ```cds using { SomeEntity } from 'some-reuse-package'; @@ -389,7 +389,7 @@ Verticalization means to adapt a given application for different regions or indu ## Inheritance Hierarchies -Sometimes you'd be tempted to create deeply nested inheritance hierarchies as you might be used to do in Java. For example, lets assume we're tempted to model something like that: +Sometimes you'd be tempted to create deeply nested inheritance hierarchies as you might be used to do in Java. For example, let's assume we're tempted to model something like that: ```cds abstract entity Grantees { // equivalent to aspect