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

Ruby on Rails capstone project - Budget app #4

Merged
merged 34 commits into from
Aug 20, 2023
Merged

Ruby on Rails capstone project - Budget app #4

merged 34 commits into from
Aug 20, 2023

Conversation

oovillagran
Copy link
Owner

Hey there

Welcome to my RoR capstone project.

Here are the Project Requirements:

You will create a Ruby on Rails application that allows the user to:

  • Register and log in, so that the data is private to them.
  • Introduce new transactions associated with a category.
  • See the money spent on each category.

Design

  • Follow these design guidelines, including:
    • Colors.
    • Typography: font face, size and weight.
    • Layout: composition and space between elements.

Interactions

  • Splash screen.

    • A simple page with the name of your app (yes, you need to choose one), and links to the sign up and log in pages.
  • Sign up and log in pages

    • The user should be able to register in the app with full name, email and password (all mandatory).
    • The user can log into the app using email and password.
    • If the user is not logged in, they can't access pages that require the user to be logged in (all the pages described below).
  • Home page (categories page)

    • When the user logs in, they are presented with the categories page.
    • For each category, the user can see their name, icon and the total amount of all the transactions that belongs to that category.
    • When the user clicks (or taps) on a category item, the application navigates to the transactions page for that category.
    • There is a button "add a new category" at the bottom that brings the user to the page to create a new category.
  • Transactions page

    • For a given category, the list of transactions is presented, ordered by the most recent.
    • At the top of the page the user could see the total amount for the category (sum of all of the amounts of the transactions in that category).
    • There is a button "add a new transaction" at the bottom that brings the user to the page to create a new transaction.
    • When the user clicks on the "Back" button (<), the user navigates to the home page.
  • "Add a new category" page

    • The user fills out a form to create a new category, indicating their name and icon (both mandatory).
    • The user clicks (or taps) the "Save" button to create the new category, and is taken to the home page on success.
    • When the user clicks on the "Back" button (<), the user navigates to the home page.

-"Add a new transaction" page.
- The user fills out a form to create a new transaction with:
- name (mandatory)
- amount (mandatory)
- categories (mandatory at least one)
- The user click (or taps) the "Save" button to create the new transaction, and is taken to the transactions page for that category.
- When the user clicks on the "Back" button (<), the user navigates to the transactions page for that category.

Testing requirements

  • Create unit and integration tests for all the most important components of your RoR application.

Technical requirements

  • You should use Postgres as your database.
  • You should use devise for authentication.
  • You should validate all user input to make sure that anyone with bad intentions cannot compromise your app.
  • You can use a view template engine of your choice (.erb, .slim, .haml).
  • The project should be deployed and accessible online.
  • Your database schema should reflect the following structure:

Thanks for your kind review and feedback

Copy link

@DuaneDave DuaneDave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @oovillagran 👋,

In my opinion, your project is ready for presentation! There is nothing else to say other than... it's time to merge it :shipit:

Good luck! 🎉

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

@oovillagran
Copy link
Owner Author

Thanks @DuaneDave !!

@oovillagran oovillagran merged commit 7b95d7d into main Aug 20, 2023
3 checks passed
oovillagran added a commit that referenced this pull request Aug 20, 2023
Merge pull request #4 from oovillagran/dev
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 this pull request may close these issues.

2 participants