Build bulk selection UI for transactions

[zachgoll]

Feature Overview

The purpose of this issue is to create UI controls to select 1 or more transactions and perform various actions on those transactions.

Not in Scope

This issue will NOT cover the actual updates—it is solely UI focused. Placeholders and cursor-not-allowed states should be added over the form submissions for now.

Requirements

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

• User can see select checkbox on each transaction
• User can select 1 or more transactions
• When selected, a bar at the bottom appears that says how many are selected
  • User sees an edit icon (placeholder, cursor-not-allowed)
  • User sees a delete icon (placeholder, cursor-not-allowed)

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!

Designs

Below are the designs you should follow while implementing this:
https://www.figma.com/design/lonJmVk3HYkwZoIO7xYP2w/Maybe-App-(Community)?node-id=3626-2572

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.

[scubamaggo]

I have tinkered with this a bit and during the implementation noticed that we have a second transaction list: The one on the dashboard.
My initial gut feeling when using the checkboxes was that they do not belong on the dashboard view, but should be kept to the Transactions view as seen in the issue description.

What is the general opinion on that?

[zachgoll]

@scubamaggo I agree with this. I'm working on cleaning up some of that in #795 which will probably make this issue quite a bit easier to work with.

I'm going to go ahead and mark this as "Planning" in the project as I think #795 should probably be completed first. If you have some ideas feel free to leave them on that issue and I'll try to get them implemented.