Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend project structure #28

Closed
4 tasks done
oli-lane opened this issue Feb 5, 2024 · 0 comments · Fixed by #37
Closed
4 tasks done

Backend project structure #28

oli-lane opened this issue Feb 5, 2024 · 0 comments · Fixed by #37
Assignees

Comments

@oli-lane
Copy link
Collaborator

oli-lane commented Feb 5, 2024

Right now, the backend is set up to have all of the routes in api/app.py. In order to make it more scalable, make the routes modular. Here is a file structure you could use:
api/
|-- src/
|----| app.py
|----| routes/
|------| __init__.py
|------| slo_county.py

Requirements:

  • Create a Chalice Blueprint in slo_county.py
  • Create a dummy route in slo_county.py that returns "Hello World!"
  • Register the blueprint in app.py
  • Test the new route (use curl in command line)

As always, make sure to run the linter and formatter and make sure everything works when you run locally!

@oli-lane oli-lane changed the title Chalice project structure Backend project structure Feb 5, 2024
@Parshana007 Parshana007 linked a pull request Feb 12, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants