Yep! The current system is split up into lots of small, modular widgets so that they can be on separate pages.
Ideally, this change would also make the teacher page store its state in the URL, rather than in state management.

You wanna tackle this next after #193, @ParkerH27?

Made a few changes to the surrounding code to make this a tad bit easier.

You wanna tackle this next after #193, @ParkerH27?

I guess so.... #193 is brain breaking

It's been 2 months. You still up for this? We need to get it done before we present (b/c it's blocking me on some other stuff).

A: Hopefully that is what I was supposed to do because it felt waaayyy too easy(that is scary)
B: You're welcome for somehow failing the Markdown test :)

A: Hopefully that is what I was supposed to do because it felt waaayyy too easy(that is scary)
B: You're welcome for somehow failing the Markdown test :)

I'll address both of these in turn, @PetalCat.

• B: It's a bug, something changed on GitHub's side. I've removed the auto-pr to fix markdownlint failures, so it works now.
• A: It's a good start. However, I'd personally recommend starting over. You moved all the code all over the place, when really all you needed to do was remove currentStageProvider and the Stage class. Then, rename _StudentView and _TeacherView to lack an underscore, annotate them with @RoutePage() as you did, and split them into two files. At that point, see what's erroring, and switch them to use routes instead of Riverpod. It should also be noted that the tests are failing because of how you configured the router. Retain the current setup, but have the main page be like WrapperPage, having children in the AppRouter singleton and using the AutoRouter widget to get children. Maybe use the guards list to bounce people to the right page? Another thing to keep in mind is that you can use query parameters for ViewCoinsStage.student, which will let you make that passable in navigation.