I just started reading your book. Great job.
I particularly like your code annotations, with notes such as
// 1 in the code keyed to the related description in your text:
- A widget’s
build()method is the entry point for composing together other widgets to make a new widget.
You have a wonderful opportunity to do a similar annotation for an
annotation that appears everywhere and that the official
Dart documentation doesn’t manage to clarify:
Nobody seems to have mentioned, in a clear way, the motivation (and the tradeoffs) behind
@override in your book and you’ll get 82 results. Unfortunately, all of them are occurrences of the annotation and, as far as I can tell, there’s not a single annotation regarding why.
In any case (whether
@override must be explicit or could be implicit), please consider providing a good description of the concept before the first appearance of
@override in section 2 (Hello, Flutter).
Thanks for an excellent book.