You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add settings molds through DSL
* Change object building to use molds
* Provide essential molds out-of-the-box
* Add support for Struct, Data, Hash out-of-the-box
Copy file name to clipboardExpand all lines: README.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ However, such gems make a lot of assumptions about why, how and what for they wi
23
23
- assuming that streamlined object generation is only useful for testing;
24
24
- (related to the previous point) assuming that there will never be a need to
25
25
have more than one configuration of a library in the same project
26
-
(I believe, this anti-pattern was popularised by Rails);
27
-
-(and related again) assuming that adding global methods or objects is a good idea.
26
+
(I believe this anti-pattern was popularised by Rails);
27
+
- assuming that adding global methods or objects is a good idea.
28
28
29
29
I notice that there is also a problem of thinking that Rails's "convention-over-configuration" approach is always appropriate, but then making configuration convoluted, instead of making it easy for the user to do the things they want in the way they want in the first place.
0 commit comments