Onwards we go.
v1.7.5 can be characterized as a refinement release. I went through "React and Flux" and "From Notes to Kanban" with my editor (thanks Jesús!). As a result we should have something that's a notch better together. I took some decompression time during this iteration and negotiated a lot towards a better future I hope.
In total 116 commits went to
v1.7.5. To make it easier to follow what happened and where, I've split up the changes below.
You can see GitHub for all changes.
npm ibits. Now
--shouldn't get mangled.
.gitignore. I've seen some people to neglect this so I felt it's good to cover. It's just one of those things that saves your nerves. :)
colors: truesetting from
devServerconfiguration. Reading from source I learned that
webpack-dev-serveractually detects for terminal colors automatically. As a result this bit of configuration can be dropped.
notesdefinition outside of the
Appcomponent. This cleans up the implementation a little.
super(). Remember that it refers to the method of the parent class.
display: inline-block;to force a minimum height to them even if there's no content at all. This way they can be edited even then.
this.notes = this.notes || ;check. This won't be needed so it can be safely dropped. The same goes for bootstrapped data in general. It just works.
@logfor logging how methods are called.
AltContainerInstead of a Decorator for clarity.
Laneid remains the same during its lifecycle so this seemed like a safe change to make.
NoteStore. While at it I bummed a couple of lines of code from it. Now it's as compact as it can get.
'../libs/item_types'as it's not a component.
We will be doing more work on this chapter to make it clearer still.
--allow-emptyto allow empty distribution commits to be made.
preversionhook does everything we need now.
I'll continue going through the content with my editor while listening to your feedback. I'm particularly interested in highlighting updated lines as that would make it easier to follow what lines of code changed during the tutorial. I believe resolving this could help to push the book quality a notch further.
Now that the content is getting solid this means I can spend more time on producing new content. I'll be focusing on typing next. Also some other plans have been put to motion but more on those later.
I think this was yet another good step towards a quality release at Amazon. Thanks for everyone involved! You make it worthwhile. :)
I hope you enjoy this release. As usual feedback and pull requests are welcome.
Remember that you can support my work by purchasing the book at Leanpub. Every little bit counts and allows me to keep it up.