Commit Timetracking #237
Assignees
Labels
Comments
uberroot4
added
enhancement
TBalint2000
added a commit
that referenced
this issue
Jun 19, 2024
Declared all the necessary classes that are going to be needed with the corresponding exports. All return values are empty and have to be replaced. Ref: #237 Time-spent: 0h45m
TBalint2000
added a commit
that referenced
this issue
Jun 19, 2024
Added Commit type and Thresholds to the config file. Branch selection requires more effort, which has to be done later. Reducers had to be reworked in order to map changes correctly. Initial values were also overwritten to be consistent. Ref: #237 Time-spent: 1h17m
TBalint2000
added a commit
that referenced
this issue
Jun 23, 2024
Added dropdown selection for branches. Corrected default value of selectedBranch to 'master' instead of 'main'. Changed dashboardState to get the state of commitTimeTracking instead of changes. This was a result of copy-pasting code Ref: #237 Time-spent: 1h22m
TBalint2000
added a commit
that referenced
this issue
Jun 25, 2024
Commit data extraction was defined without time extraction. Interfaces for necessary structures like props and commit data are defined. For future work, replace time with proper estimates or actual time extraction from commit message, apply filtering based on config options, and getting the maximum values of the bars for scales. Ref:#237 Time-spent: 1h10m
TBalint2000
added a commit
that referenced
this issue
Jul 15, 2024
Added commitType to chart data. Real type evaluation remains to be done. Ref:#237 Time-spent: 0h5m
TBalint2000
added a commit
that referenced
this issue
Jul 15, 2024
Fasttext commit classification had to be moved to backend, because the library only works in node.js. To that end, a new endpoint was created to serve the API calls for commit type classification. Ref:#237 Time-spent: 0h30m
TBalint2000
added a commit
that referenced
this issue
Jul 15, 2024
This finalizes the processing step of commit data. Next step is to visualize the data that was gained from processing. Replacing the constants and handling the issue with Promise is in future work. Ref:#237 Time-spent: 3h02m
TBalint2000
added a commit
that referenced
this issue
Jul 16, 2024
Made corresponding functions async and used await to fetch value of promise. Ref:#237 Time-spent: 0h32m
TBalint2000
added a commit
that referenced
this issue
Jul 16, 2024
The first draft of the graph was implemented. This includes both barcharts with the nodes in the middle. A lot of values in styling are hardcoded and the graph is not responsive. Both aspects remain to be corrected. Furthermore, the hover-over for the nodes for more information has to be also implemented. Potential for additional work would be the adjustment of the bars depending on the probability of the label. Ref:#237 Time-spent: 4h0m
TBalint2000
added a commit
that referenced
this issue
Jul 18, 2024
Navigation of pagination was adjusted, so that it doesn't appear, if there is only one page, and the corresponding arrows don't appear on the first/last page. Furthermore, the width of the bars was fixed and now appears with the same width as the other pages. Ref:#237 Time-spent: 0h12m
TBalint2000
added a commit
that referenced
this issue
Jul 22, 2024
In two places, != was replaced by !==, which caused the bug. Ref:#237 Time-spent: 0h40m
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Themenvorschlag.pdf
The text was updated successfully, but these errors were encountered: