Skip to content
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

[#2161] One-Stop Config File for Code Portfolio #2172

Closed
wants to merge 30 commits into from
Closed
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
2db2ac0
Update with report config YAML files
georgetayqy Mar 25, 2024
202d247
Undo SummaryJson changes
georgetayqy Mar 25, 2024
f64f6ed
Update ReportConfiguration to support branches
georgetayqy Mar 27, 2024
356299a
Update Report Configuration docs
georgetayqy Mar 27, 2024
ffd4912
Merge branch 'master' into 2161-code-portfolio
georgetayqy Mar 27, 2024
2cbb662
Update YAML format
georgetayqy Mar 28, 2024
9190fb0
Fix environmental error
georgetayqy Apr 1, 2024
b611f29
Implement Markdown Parser
georgetayqy Apr 2, 2024
6573637
Fix test cases
georgetayqy Apr 2, 2024
6c5e401
Add blurbs on frontend (#2186)
sopa301 Apr 4, 2024
4259db3
Merge branch 'master' into 2161-code-portfolio
georgetayqy Apr 4, 2024
43f1c14
Add tests for BlurbMap and ReportConfiguration
georgetayqy Apr 4, 2024
d5fd31a
Remove manual testing artefact
sopa301 Apr 4, 2024
6e58493
Upgrade checkstyle and fix checkstyle errors
georgetayqy Apr 5, 2024
7924629
Revert "Upgrade checkstyle and fix checkstyle errors"
georgetayqy Apr 5, 2024
cbf622d
Update regex
georgetayqy Apr 8, 2024
fa95f75
Remove unused methods
georgetayqy Apr 8, 2024
4299ff2
Update Regex to accept 0 or more characters
georgetayqy Apr 8, 2024
1145f8e
Modify css
sopa301 Apr 8, 2024
7c94fea
Merge branch '2161-code-portfolio' of https://github.com/reposense/Re…
sopa301 Apr 8, 2024
6ee3249
Update Yaml file format
georgetayqy Apr 8, 2024
48c873b
Add blurbs to frontend files
sopa301 Apr 8, 2024
50f6ec6
Fix style
sopa301 Apr 8, 2024
941f420
Fix style
sopa301 Apr 8, 2024
6dd383b
Move blurb parsing into ArgsParser
georgetayqy Apr 11, 2024
d628e85
Merge branch '2161-code-portfolio' of https://github.com/reposense/Re…
georgetayqy Apr 11, 2024
68ea84e
Fix tests
sopa301 Apr 11, 2024
28d9c84
Change config files
sopa301 Apr 11, 2024
83329cf
Update blurb map parsing
georgetayqy Apr 11, 2024
f70ead4
Merge branch '2161-code-portfolio' of https://github.com/reposense/Re…
georgetayqy Apr 11, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions docs/ug/configFiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,12 +107,22 @@ e.g.: `example.java` in `example-repo` can either be in the `test` group or the

<!-- ==================================================================================================== -->

## `report-config.json`
## `report-config.yaml`

You can optionally use `report-config.json` to customize report generation by providing the following information. ([example](report-config.json))
You can also optionally use a `report-config.json` file to quickly define the repository information for the repositories you are interested in tracking and generate your very own code portfolio.

View this [example](report-config.yaml) for a better understanding of what repository information is required.

**Fields to provide**:
* `title`: Title of the generated report, which is also the title of the deployed dashboard. Default: "RepoSense Report"
* `repoUrl`: The URL to your repository of interest
* `reportTitle`: Title of the generated report, which is also the title of the deployed dashboard. Default: "RepoSense Report"
* `authorDisplayName`: Name of the author to track in the repository.
* `authorGithubId`: The GitHub username of the author to track in the repository.
* `branches`: A list of branches with their associated blurbs.
* `name`: Name of the branch to track
* `blurb`: Blurb to include with the branch
* `startDate`: The start date of analysis for RepoSense. Default: "2020-01-01"
* `endDate`: The end date of analysis for RepoSense. Default: "9999-12-32"

<!-- ==================================================================================================== -->

Expand Down
3 changes: 0 additions & 3 deletions docs/ug/report-config.json

This file was deleted.

11 changes: 11 additions & 0 deletions docs/ug/report-config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
repoUrl: github.com/user/repo
reportTitle: RepoSense Report
authorDisplayName: Sample Author
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not needed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damithc Sure thing, will remove these from the YAML file and other associated classes in a future commit.

authorGithubId: Sample Author Github ID
branches:
- name: Branch 1
blurb: Blurb 1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blurb should allow a few paragraph of markdown text. So, yml might not be the right format for this config file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damithc There are ways to incorporate multi-line strings into YAML files here, we could perhaps include this into the docs to let users know how they can tailor the blurbs to suit their use cases (multi-paragraph vs long single paragraph text)

- name: Branch 2
blurb: Blurb 2
startDate: 2020-01-01
endDate: 9999-12-31
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #2161 (comment) for an example that seems intuitive from the user POV

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damithc Just wanted to clarify, do you mean that we should include the configs within the markdown files itself, and have the backend parse the markdown files and then generate the reports, or that the overall order/style/keys in the YAML file should match what was used in the example provided?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asdfghjkxd I wasn't specifically using markdown either. It is just a custom format that makes sense from the user's point of view. I'm fine if something close can be achieved by YAML or some other commonly-used format, provided it makes sense from the user (i.e., the user shouldn't have to do a lot of extra work just to conform to the file format)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damithc I see, sure thing, we will try to design a user-friendly and convenient config file format and update this PR and parent issue with any new findings/improvements!

Loading