The notes above is what I was thinking on while reading the book. That does not mean something must be changed. Instead I hope they end up providing a guided reflection.
1: "active hook called" instead of "activate hook called"
2: "This strategy for loading records works well if we know that all the records the association depends on are already in the store, or if there is a low number of records to side-load." (seems like "this strategy" points to two different strategies rather then one single strategy)
3: "{async: true)" -- a parenthesis used instead of a curly bracket
4: Code @ page 118, if this code works, I'd say clarification is in order:
Page 118 model hook suggestion:
model: function(params) {
return this.store.find('friend', params);
}
My guess on correction based on http://emberjs.com/api/classes/Ember.Route.html#method_model
model: function(params, transition, queryParams) {
return this.store.find('friend', queryParams);
}
5: Page 121: CI could use a reference to what it means
6: Page 125: DSL could use a reference to what i means (still have not figured it out)
7: Page 128: "We are currently able to structure our projects using pods or by grouping items by their time, but the way forward is to start using pods." --- I might simply not get it even though it makes sense, but if it does, maybe you can reformulate this sentence so I might understand it. (Key confusions: "by their time" and "but the way forward is to start [...]")
8: Page 131: CORS could use a reference to what it means
9: Page 134: Fingerprinting, remark on why doing this is useful or reference to another source to explain it would be nice.
10: Page 135: Why not use the public folder and place the fonts there? Ah because you might get updates using bower, my bad. But a remark about this could be considered.
11: Page 137: PaaS could use a reference to what it means
12: PODS --- I was thinking to myself that I didn't mind changing to a POD structure, but I don't mind having it as it is by default. And I felt uncertain if you meant that the PODS structure were to become recommended but was not yet. If so, I'd transition already.
Awesome book! You have really helped me a lot! My knowledge was like a jenga-tower in bad shape, but now it feels a lot better.
Thank you for your efforts in writing this book, it made my day!
The notes above is what I was thinking on while reading the book. That does not mean something must be changed. Instead I hope they end up providing a guided reflection.
1: "active hook called" instead of "activate hook called" 2: "This strategy for loading records works well if we know that all the records the association depends on are already in the store, or if there is a low number of records to side-load." (seems like "this strategy" points to two different strategies rather then one single strategy) 3: "{async: true)" -- a parenthesis used instead of a curly bracket 4: Code @ page 118, if this code works, I'd say clarification is in order: Page 118 model hook suggestion:
model: function(params) { return this.store.find('friend', params); } My guess on correction based on http://emberjs.com/api/classes/Ember.Route.html#method_model model: function(params, transition, queryParams) { return this.store.find('friend', queryParams); } 5: Page 121: CI could use a reference to what it means 6: Page 125: DSL could use a reference to what i means (still have not figured it out) 7: Page 128: "We are currently able to structure our projects using pods or by grouping items by their time, but the way forward is to start using pods." --- I might simply not get it even though it makes sense, but if it does, maybe you can reformulate this sentence so I might understand it. (Key confusions: "by their time" and "but the way forward is to start [...]") 8: Page 131: CORS could use a reference to what it means 9: Page 134: Fingerprinting, remark on why doing this is useful or reference to another source to explain it would be nice. 10: Page 135: Why not use the public folder and place the fonts there? Ah because you might get updates using bower, my bad. But a remark about this could be considered. 11: Page 137: PaaS could use a reference to what it means
12: PODS --- I was thinking to myself that I didn't mind changing to a POD structure, but I don't mind having it as it is by default. And I felt uncertain if you meant that the PODS structure were to become recommended but was not yet. If so, I'd transition already.
Awesome book! You have really helped me a lot! My knowledge was like a jenga-tower in bad shape, but now it feels a lot better.
Thank you for your efforts in writing this book, it made my day!
Best regards Erik aka consideRatio