metal-gogo / habits Goto Github PK

Right now, the form for creating commitments is on the dashboard.

For some reason, the test:coverage script is not working as expected.
Find out what's wrong and fix it.

The application needs a logo.

It would be great to have a <FullPageLoader /> component.
When loading the app we have the following text:

Loading...

That's not super nice.

At the moment, we only console.log the errors. But this causes linting warnings and is not helpful for the users.

Let's find out what's the best way to manage these situations in a scalable way. Maybe a generic notification?

Follow this pattern:

• Add an application header.
• Add an application footer with main actions.
• Make the application change the content only in the inside of the shell.

Convert the application into a PWA.

For this we will need:

• Add Offline support.
• Add application manifest.
• Register service worker.

Add Storybook UI to showcase our components.

https://storybook.js.org/docs/react/get-started/introduction

We are using Firestore as our database.
We should document how we are using it. Also, add documentation on how to test things relevant to Firestore.

Once we have a logo in place, we should have icons for the application. Starting with the favicon, then go to the possible icons for iOS, Android and Windows devices.

It could be a better experience for the user if the creation is made through a wizard explaining step by step everything.

We have some Firestore rules for users. and commitments. We should add unit testing for them to be sure that they are doing what it's they should do.

We are querying for the commitments, but we are logging them instead of showing them.

• Create a <CommitmentCard /> component.
• Create a <CommitmentList /> component.
• Show commitments on .

• Check if it is possible to do code splitting by route with reach router.
• If possible, enable it for our routes.

• Setup dependabot to make sure we have our dependencies up to date.
• Update dependencies that dependabot suggest.

Add a CTA to add if the user kept on with the commitment.

This should generate information on:

• Current active streak. If the user kept the commitment.
• Current inactive streak. If the user didn't keep the commitment.
• Longest Streak.

The Header works only for Desktop.
On mobile devices it gets broken

Setting up the testing for Firebase within the app is not as straight forward as one would hope.
Study about it and make it work.

Some references:

• https://github.com/soumak77/firebase-mock
• https://www.robinwieruch.de/firebase-test

• Whenever a Feature or a Bugfix is merged into the develop branch a deployment should be made to the Staging environment.
• Whenever a Release or a Hotfix is merged into the master branch a deployment should be made to the Production environment.
• Add relevant documentation.

If the user doesn't have any commitment, show an empty state to encourage the user to create a commitment.

One easy optimization on Firestore usage is to check the user before updating them on https://github.com/metal-gogo/habits/blob/master/src/contexts/auth/auth.js#L21

The user should be able to delete a commitment that he doesn't want anymore. Before tackling this, must decide if we make a soft delete or a hard delete.

At the moment if the user gets to a route that doesn't exist, we show the default route. This is the Dashboard page for a signed-in user, and Home page for a guest user.

We have a page named NotFound that should be used for that.

Whenever a Pull Request is made, there should be some checks:

• Lint the application.
  • There must be no lining errors.
• Test the application.
  • There must be no failing test.
  • Should report testing coverage.
• Add relevant documentation.