STRETCH - NEW USER NAVIGATION PROCESS

[keanacobarde]

User Story

I, as an incoming user - who falls into any categories highlighted within the proposal of this application - will need to provide some data on startup. That being:

• Preliminary category names
• What I'm looking to save up for/percentages of my income that I'm comfortable with saving up for
• My current monthly savings (this should be the first question asked, as OnPaper revolves around this concept)
• Some information/suggestions as to how much you should save up for.

Acceptance Criteria

WHEN, a user who has never signed in before signs in, they should be met, immediately with a form requesting for them to supply some information. This form will request for the following:

• Monthly Income
• Some of the things they value (the answer to these questions will determine the categories that are made)
• How MUCH they 'value' each category (some sort of slider, will determine whether the percentages of their monthly income that's allocated to a specific category)
• Submit button. This will render everything. The categories, the timeline with the user specific months, and THEN all of the user inputted data - such as categories, values, etc.

There should also be a function that allows for the user to opt out of the form; however, this may need to be something that's implemented later.

Dependencies

N / A - All components within this issue ticket will be newly created, outside of the API calls which communicate with the FireBase. That won't be!

Dev Notes

• Will most likely need to make use of some FireBase functions/context driven functions that query whether or not the user is new.
• May require an update to the ERD; however, there's no new entity being created upon the start - all information is updated on pre-existing entities - just for a different user. Take a look at it and determine whether one is required.
• Create a wireframe. The form may best be used in conjunction with an MUI stepper. Document your thoughts first before attempting to build/import any components.
• Figure out the process of patching and posting to the FireBase. What order does it need to happen in? Is it all happening at once? Figure out the flow of execution.

[keanacobarde]

UPDATES:

• [x] Handle the rendering issues for months for new users.
• [ ] Create the optimization, automatic allocation process for current users. Or, at least setup the skeleton so that the process can be ported from current users to new users.

[keanacobarde]

LOGIC FOR CHECKING THE ACCOUNT AGE:

  const checkingAccAge = () => {
    const timeDiff = parseFloat(user.metadata.b) - parseFloat(user.metadata.a);
    if (timeDiff < 2) {
      const monthsArray = [
        'January', 'February', 'March', 'April', 'May', 'June',
        'July', 'August', 'September', 'October', 'November', 'December',
      ];
      monthsArray.forEach((monthInd) => {
        const payload = {
          month: monthInd,
          year: date.toLocaleDateString('default', { year: 'numeric' }),
          earnings: 0,
          uid: user.uid,
        };
        createNewMonthlyIncome(payload).then(({ name }) => {
          const patchPayload = { firebasekey: name };
          updateIncome(patchPayload).then(console.warn);
        });
      });
    }
  };