-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/145: Database Changes #150
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- instead of storing the signature of an author in the `signature` attribute of commits, a connection is used - the frontend still uses the `signature` attribute, but it is inferred using the connection - #145
- instead of using the `mentions` attribute in issues - #145
- commits were not sorted with new localDB function, which broke the Changes/Version mode of the Code Hotspots visualization. - #145
- instead of the `sha`/`ref` attributes in the builds collection, the commits-builds connection is used. - #145
- Because the `builds` connection does not have a `sha` attribute anymore, the Histogram endpoint was broken both in the serverDB and the localDB. - #145
- instead of using the `history` and `parents` attributes, the commits-commits connection is used. - the graphql service infers the parents directly, as does the localDB when accessing commits. This means the `parents` attribute can still be queried, even if it's not in the DB anymore. - query times are much faster, DB export files significantly smaller - #145
- fixed bug where filepicker crashes when new files are added in the project directory but ownership has not yet been indexed
- when querying commits using the seerverDB, commits that are earlier than the specified earliest date should only be discarded after the history has been calculated for all commits. Otherwise, history calculation would not work properly. - #145
- fixed bug where sprint visualization crashes when no sprints are defined - also fixed minor styling/behaviour bugs of new TabCombo component
- fixed bug that led to test fails
nuberion
approved these changes
Sep 12, 2023
MaximilianZenz
approved these changes
Sep 12, 2023
Open
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
signature
attribute in commitsmentions
attribute in issuesparents
/history
attributes in commitssha
/ref
attributes in builds