vincentrohde / harvest-dashboard

An open-source, third-party React client for the Harvest API V2 (time-tracking) ⏰

Hey folks 👋

Welcome to my Github page! My name is Vincent Rohde. I am living in Berlin (Germany 🇩🇪) and currently working for Endava.

How to reach me 📫

If you want to reach out for a collaboration, feel free to contact me via [email protected]
For extra content check out my website vincentroh.de

Read more from me via Medium

A short summary about myself 👨🏻‍💻

• Passionate Front-end developer with an eye for outstanding visual design (my secret superpower 😉).
• Implementing personal projects and working freelance in my free-time.
• Focusing on JavaScript (3+ years experience) and it's technologies.

My tech stack 🧬

• JavaScript / ES6 (3+ years experience)
• React (3+ years)
• Next.js (2+ years)
• TypeScript (2+ years)
• Node.js (3+ years)
• Docker (2+ years)
• SCSS (3+ years)

Projects I am very proud of 💖

The video library of the Austrian 🇦🇹 national public service broadcaster (ORF)

Handling 400,000 visits each day in 2020 (Source)

Harvest Dashboard ⏰

Open-source, third-party React client for the Harvest API V2 (time-tracking)

harvest-dashboard's Issues

[Feature] Testing

[Refactor] Rename Category to Group

IS State:

Across the project there are a lot of files, that refer to "Categories" (name if something could be either a projects or a tasks). An example would be the ./client/src/types/Categories.ts file.

SHOULD State:

Whenever you find a reference to "categories" / "category" this should be renamed to "groups" / "group".

Example

Before

./client/src/types/Categories.ts

export type categoriesType = CategoryInterface[];

export interface CategoryInterface {
    id: number;
    name: string;
}

After

./client/src/types/Groups.ts

export type groupsType = GroupsInterface[];

export interface GroupInterface {
    id: number;
    name: string;
}

When you have updated the naming, please make sure to update the imports and references to the new name as well.
So if you renamed for example a function, make sure that wherever the function was used, the name is updated.

When everything is updated, please make sure, that nothing broke during renaming 👍

[Docker] Add no-cache option to dev install scripts

IS State
Currently the npm run dev:install (https://github.com/vincentrohde/harvest-dashboard/blob/develop/package.json) / make dev:install (https://github.com/vincentrohde/harvest-dashboard/blob/develop/Makefile)scripts uses the --no-cache flag.

SHOULD State
Both files (Makefile and package.json) should have two options:

1. dev:install (doesn't use --no-cache flag at the end)
2. dev:install:nocache (uses --no-cache flag at the end)

This is a good issue to learn more about the project's Docker-Compose setup

[Feature] Sticky Header for the Frontend

IS State:

Currently the title is just above the DatePicker.

SHOULD State:

It would be great, if the title is part of a sticky colorful header. This would improve the UI. The header doesn't have to be extra fancy. Something minimal like this would work well:

How To Reproduce

Start the project and see if there's a Header with title, instead of the title just floating around 😉

Convert to Next.js

[Bug] Patch / Release Action not working

git config --global --add safe.directory /github/workspace
fatal: unsafe repository ('/github/workspace' is owned by someone else)

actions/checkout#760

[Feature] Setup Prettier

To promote a standard code format, it would be great if the project makes use of Prettier (https://prettier.io/).

Acceptance Criteria

• Prettier is installed in the project's root ./package.json

• A configuration is set up in the project's root directory, with the following values:

printWidth: 100
tabWidth: 4
singleQuote: true
bracketSpacing: false
endOfLine: 'auto'
trailingComma: 'all'

• Formatting script is implemented in the project's root ./package.json

"scripts": {
    "format-code": "..."
}