From 4b70b7852038c7140ec6717fd311b6d81b562ae0 Mon Sep 17 00:00:00 2001 From: Victor Justo V Date: Sat, 5 Sep 2020 12:39:07 +0200 Subject: [PATCH] Typo in 5_consider_code_generators_carefully.md --- style/5_consider_code_generators_carefully.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/style/5_consider_code_generators_carefully.md b/style/5_consider_code_generators_carefully.md index 91560ea..369a924 100644 --- a/style/5_consider_code_generators_carefully.md +++ b/style/5_consider_code_generators_carefully.md @@ -22,7 +22,7 @@ Boilerplate generators are the simplest form of code generation. They can be fur * Generators that produce scaffolding that is checked into version control and modified. * Generators that produce new classes from a model. The generated code is not normally checked into version control. -We recommend that the first type are using sparingly, if at all. This is discussed further in "Know How to Implement Hashcode and Equals". +We recommend that the first type are used sparingly, if at all. This is discussed further in "Know How to Implement Hashcode and Equals". Generating code from a model (such as a schema or grammar) can be a useful approach as long as the generated code is not modified and is packaged separately. If generated and non-generated code are packaged within the same module then this can start to cause friction (see below).