Add error message and TypeError for invalid route in App class

[elviskahoro]

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

New Feature Submission:

• Does your submission pass the tests?
• Have you linted your code locally prior to submission?

Changes To Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.

a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

[elviskahoro]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Trunk Check Workflow #3787
• Add error message and TypeError for invalid route in App class #3786 👈
• Adding trunk config with constraints to ignore test files #3783 : 1 other dependent PR (#3784 )
• .gitmodules and .trunk/config Submodule Addition #3782
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @elviskahoro and the rest of your teammates on Graphite

[elviskahoro]

@ElijahAhianyo going to temporarily close since match case came out in Python 3.10