One project across chapters

In my opinion, there should be one project we build upon across chapters as long as it’s still regarding that one app.

Right now I implement whatever’s needed for the chapter, then go to the next chapter where the book mentions a file that’s not present in my current project. I have no choice but to open a new project - starter_for_chapter_X. That feels awful.

I suggest the start project has all the files necessary that we will not be implementing ourselves. If you want, you can create various checkpoints with final_for_chapter_X in case the user diverges from the curriculum too far.

Edit: I also have to repaste my API keys for every project. Absolutely not fun.

3 Likes