Hi, Laura!

Is the name of this variable incorrect?!

This was because there's no typing for the styled components theme and, therefore, the typescript didn't return an error.

I will be sending a PR for correction.

Requested changes

Improve the docs, regarding the following topics:

• Show examples
• Improve features list
• Improve installation instructions
• Add contributing guidelines

Motivation

Improve the experience of contributors

Requested Changes

Install and configure i18n in order to provide Portuguese/English support

Motivation

The application will reach out to more users, both PT and EN speakers.

Requested Changes

Use react-query library to handle with server-side data. Install it and create hooks that isolate the fetch logic, eg: useRepositories.

Motivation

Currently, data is being fetched without dealing with important strategies such as a cache, or data re-invalidation when focusing the UI. react-query handles all the complexity of cache and re-invalidation, by also exposing a nice layer of abstraction.

Requested Changes

Update CRA to v4.1

Motivation

The CRA v4.0 ships the fast refresh feature, which improves the development experience.

Besides, there are also other improvements that can be important for this codebase:

• Support to TS v4
• Support for ESLint 7

Requested Changes

• Break the page into more components (Follow the "Show, don't tell" principle)
• Define type definitions on separate files, such as types.ts
• Use the https://github.com/soyguijarro/react-storage-hooks package to store values on local storage, since it deals with the cases where local storage is inactive on the browser.
• Use absolute imports with TS paths
• Use named exports to improve auto-import and nomenclature refactors

Motivation

The current architecture doesn't have a good approach regarding the following points:

• Componentization
• Location of type definitions
• Use of local storage without verifying its existing

And regarding code style:

• Use of relative ones with multiple levels '../../' and making reading difficult
• Use of React.FC instead of explicitly setting the type for the component props. Refer to facebook/create-react-app#8177 in order to see the downsides of using it

Tasks

• Improve componentization
• Move type definitions to separate files
• Use local storage with hooks packages to avoid accessing it directly
• Use absolute import paths instead of relative ones with multiple levels '../../'
• Remove React.FC and explicitly set the type for the component props. Refer to facebook/create-react-app#8177 in order to see the downsides of using it