Code-4-Community / Code-4-Community/bcan

Dev ticket backlog/things that need to be done

Open
#350 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Frontend

  • Cashflow
    • Make it so you are able to check and uncheck certain cost or revenues to test out how the cashflow would look like without certain things(Future feature)

Backend

  • Make it so our emails don't go to spam

Misc

4/2

  • Grants get added to revenues when being fetched
  • Amend frequency to cost and update everywhere
  • When creating a grant that grant gets shown after creation is successful
  • When a user updates their email we need to update the bcan poc on all grants
    • Could make this a backend route
  • Add in more action confirmations

4/9

  • Warn user that application date is after the due when they are creating and editing a grant don't allow them submit
  • Fix edit revenue so when a revenue name tries to be set to the name of another revenue it doesn't delete a revenue(base changes off of lyannes edit cost)
  • Jane is updating the chart with the cost and revenue data(she highkey knows her ticket so you could check in with her if you think you are missing anything)
  • Streamline edit and add revenue into one component you can base your work off of janes pr for edit cost
    • Ensure the revenue name is on the left like the edit cost is(basically just make the cost and revenue edit/add look similar)
    • Ensure any backend errors are shown in the component
  • Have a timer that refetches everything "(all of the fetch methods and all of the app data) every 5 minutes also on full page reload all data is refetched

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue is a backlog containing unrelated frontend, backend, and miscellaneous work rather than one defined change. Start by separating an item into its own issue, then identify the relevant frontend or backend entry point and any existing chart, grant, revenue, cost, or fetch code it mentions. Done criteria and tests must be specified for the selected item.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.