fix(curriculum): improve tests and instructions for Expense Tracker project

[Dario-DC]

Checklist:

• I have read and followed the contribution guidelines.
• I have read and followed the how to open a pull request guide.
• My pull request targets the main branch of freeCodeCamp.
• I have tested these changes either locally on my machine, or GitPod.

Closes #52722
Closes #53135
Closes #53463
Closes #52580

[zairahira]

Reviewed till step 20.

[zairahira]

I have reviewed the project.
Provided that match/ case have not been introduced in the curriculum, I think this project can incorporate that in place if if..elif statements used to create the menu.

@ilenia-magoni, @fhsinchy, @Dario-DC What do you think?

[Dario-DC]

I have reviewed the project. Provided that match/ case have not been introduced in the curriculum, I think this project can incorporate that in place if if..elif statements used to create the menu.

@ilenia-magoni, @fhsinchy, @Dario-DC What do you think?

This is the first time that elif is used. Personally, I'd keep the current code.

[ilenia-magoni]

Everything good, other than: I have doubts on the last step. We never introduce how to work with multiple fails, so it's kind of suddend and a bit of a whiplash to have if __name__. I would totally want to have it taught, but I would see it in a proper multifile project.

[Dario-DC]

Everything good, other than: I have doubts on the last step. We never introduce how to work with multiple fails, so it's kind of suddend and a bit of a whiplash to have if __name__. I would totally want to have it taught, but I would see it in a proper multifile project.

I'm okay with removing that step from this project. The password generator is the the first project in which we import something, and probably it makes sense to not use if __name__ == '__main__' before we explain how to import a module. In my opinion, if we decide to remove it, we should remove it from the case converter, too.

What do you think? @ilenia-magoni @zairahira @fhsinchy @larymak @ihechikara

[larymak]

Everything good, other than: I have doubts on the last step. We never introduce how to work with multiple fails, so it's kind of suddend and a bit of a whiplash to have if __name__. I would totally want to have it taught, but I would see it in a proper multifile project.

I'm okay with removing that step from this project. The password generator is the the first project in which we import something, and probably it makes sense to not use if __name__ == '__main__' before we explain how to import a module. In my opinion, if we decide to remove it, we should remove it from the case converter, too.

What do you think? @ilenia-magoni @zairahira @fhsinchy @larymak @ihechikara

To maintain clarity and ensure a smooth learning curve, I'm in favor of removing the if __name__ == '__main__' step from both the password generator and case converter projects for now. So this will mean entirely getting rid of the respective steps and introducing a new approach right?

[Dario-DC]

To maintain clarity and ensure a smooth learning curve, I'm in favor of removing the if __name__ == '__main__' step from both the password generator and case converter projects for now. So this will mean entirely getting rid of the respective steps and introducing a new approach right?

My proposal is to remove it from the expense tracker and the case converter. And keep it in the password generator, since we talk about importing modules in that project.

If we remove it, we should simply delete the step in which we create if __name__ == '__main__' and keep the function call which is currently inside it.