Skip to content

Typo in 5_consider_code_generators_carefully.md #39

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Typo in 5_consider_code_generators_carefully.md #39

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
2 changes: 1 addition & 1 deletion style/5_consider_code_generators_carefully.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down