Skip to content

Commit

Permalink
Merge pull request #10438 from qmonmert/typo280724
Browse files Browse the repository at this point in the history
Typo
  • Loading branch information
murdos authored Jul 28, 2024
2 parents 770d724 + d349b97 commit 2f4fd8e
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions documentation/hexagonal-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ There is another **AWESOME** compilation time feedback coming not directly from

With just those two you can totally fix lots of mistakes with `firstname` and `lastname` inversions in method parameters: if you send the wrong one it just won't compile!

Then, a little bit slower than compilation, comes automated tests. As seen earlier this architecture eases testing so you'll be able to get fast (counting in seconds here) and reliable feedbacks from tests.
Then, a little bit slower than compilation, comes automated tests. As seen earlier this architecture eases testing so you'll be able to get fast (counting in seconds here) and reliable feedback from tests.

We said earlier that pairs feedbacks were the fastest ones but what about business experts feedback? Using "classic" (Controller, Service, Repository) architecture we have to build a whole "thing" to hope for a business expert feedback. Here, the Domain Model code is so close to the business that it's really easy to sit at a screen with a business expert and to get feedbacks from that! Of course, you'll probably have to explain some "coding stuff" BUT you will be able to get feedbacks from the business expert on any given piece of algorithm really early!
We said earlier that pairs feedbacks were the fastest ones but what about business experts feedback? Using "classic" (Controller, Service, Repository) architecture we have to build a whole "thing" to hope for a business expert feedback. Here, the Domain Model code is so close to the business that it's really easy to sit at a screen with a business expert and to get feedbacks from that! Of course, you'll probably have to explain some "coding stuff" BUT you will be able to get feedback from the business expert on any given piece of algorithm really early!

### Delay infrastructure choices

Expand Down
2 changes: 1 addition & 1 deletion documentation/module-creation.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ And this is it for this part of the documentation... Of course, you can do a lot

### Dependency resolution

- In the `src/main/resources/generator/dependencies` folder, different files are maintained to handle the dependencies for different tools/frameworks such as docker, maven, angular etc.
- In the `src/main/resources/generator/dependencies` folder, different files are maintained to handle the dependencies for different tools/frameworks such as docker, maven, angular, etc.
- You can add the dependencies required for your new module in the respective files in the `dependencies` folder.
- The dependency versions are then automatically managed by the dependabot.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,5 @@ Changelog scripts MUST tell explicitly which keyspace is used:
- by using `USE myKeyspace;` directive at the beginning of a script
- or by prepending each table with the keyspace it belongs to: `CREATE TABLE IF NOT EXISTS myKeyspace.myTable`

Second approach is recommended: it allows to not switch keyspace at runtime if there are many of them.
Second approach is recommended: it allows not switching keyspace at runtime if there are many of them.
See [warn-if-set-keyspace section](https://docs.datastax.com/en/developer/java-driver/latest/manual/core/configuration/reference/) for more info.

0 comments on commit 2f4fd8e

Please sign in to comment.