Feature: Add transaction category management

[zachgoll]

Feature Overview

The goal of this feature is to enable a user to manage all of their transaction categories from settings and inline.

Requirements

If there is a missing / incorrect requirement, please leave a comment before starting work on this.

• User can view all of their categories in settings
• User can delete a category
  • from settings page
  • from inline transaction view
• When a user deletes a category, they can optionally select a new category to re-assign transactions to
• User can edit the name and color of an existing category
• User can create a category
• Tests written for all CRUD controller actions and wherever appropriate
• i18n translations provided where necessary for en.yml
• Ensure that both settings view (/transactions/categories) and inline (/transactions) work well together. There are already a few partials created for editing/creating that might be helpful for this issue

Implementation Suggestions

Below are some ideas for implementation to get you started. Use your best judgment here—if there's a better way to do things, go for it!

• If you're not seeing any categories in your local app, here's where those should be auto-generated -

  maybe/app/controllers/registrations_controller.rb

  Line 18 in f5f6248

  Transaction::Category.create_default_categories(@user.family)

• Improvement: review categories dropdown on transactions #659 outlines a bug that happens when editing a category inline, which will likely affect this issue and need to be fixed

Designs

Below are the designs you should follow while implementing this:

https://www.figma.com/file/lonJmVk3HYkwZoIO7xYP2w/Maybe-App-(Community)?type=design&node-id=3188-1313&mode=design&t=4eaJRTzT6AYU5CNv-0

Reminders

• Make sure to review our contributing guidelines before starting on an issue
• We do our best to define a clear spec for new features and fixes, but think of them as "suggestions", not "hard requirements". We welcome ideas and suggestions!
  • If you see missing requirements to this issue, please leave a comment below explaining what is missing and why it is important.
  • If you see a requirement that you think is incorrect or not optimal, please leave a comment explaining what you think needs to change below.

Bounty

There is a $250 bounty on this. To participate in the bounty:

1. Comment /attempt #679 to indicate you plan on working on this.
2. Submit a draft PR once you start and include /claim #679 along with your general game plan for how you intent to implement this.
3. Change out of draft mode on the PR once you're ready to submit your attempt.
4. Include a short video showing functionality in your PR (drastically speeds up us approving).

In the event of multiple attempts, we generally pick the one that most closes matches the scope with the cleanest code and test coverage (when appropriate).

NOTE: Given the speed at which we're moving on the codebase, we don't assign issues or "give" issues to anyone.

[Shpigford]

/bounty $250

[algora-pbc]

💎 $250 bounty created by maybe-finance
🙋 If you start working on this, comment /attempt #679 along with your implementation plan
👉 To claim this bounty, submit a pull request that includes the text /claim #679 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to maybe-finance/maybe!

👉 Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @josefarias	Apr 27, 2024, 12:54:12 AM	#688

[josefarias]

/attempt #679

Algora profile	Completed bounties	Tech	Active attempts	Options
@josefarias	3 maybe-finance bounties	Ruby, CoffeeScript, TypeScript & more		Cancel attempt

[algora-pbc]

🎉🎈 @josefarias has been awarded $250! 🎈🎊

• Share on socials
• Give feedback