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

[#2283] Display time periods for each repository #2303

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

Airiinnn
Copy link
Contributor

@Airiinnn Airiinnn commented Feb 17, 2025

Fixes #2283

Proposed commit message

Add frontend support for specifying individual repository time periods

Previously, there is no way to indicate the different time periods for
each repository.

Let's display date indicators to show the time periods for each
repository.

Other information

Changes:

  • Date indicators are always visible now.
  • Date indicators should display the tighter date range (between the dates provided in summary.json and filter range). Refer to last summary chart in screenshot to see intended behavior.

Old:

image

Previously, date indicators are only visible when "trim timeline" is enabled.

image

New:

image

@github-actions github-actions bot requested a deployment to dashboard-2303 February 17, 2025 02:59 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 February 17, 2025 02:59 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2303 February 17, 2025 03:00 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 February 17, 2025 03:00 Abandoned
@Airiinnn Airiinnn force-pushed the 2283-fe-display-individual-time-periods branch from 49ce107 to 985cdb8 Compare February 17, 2025 03:00
@github-actions github-actions bot requested a deployment to dashboard-2303 February 17, 2025 03:00 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 February 17, 2025 03:00 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2303 February 17, 2025 03:20 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 February 17, 2025 03:20 Abandoned
@Airiinnn
Copy link
Contributor Author

On hold. Waiting for backend changes to be merged to add the cypress tests

@damithc
Copy link
Collaborator

damithc commented Feb 17, 2025

@Airiinnn For UI changes, also give before-and-after screenshots in the PR.

@github-actions github-actions bot requested a deployment to dashboard-2303 March 9, 2025 15:41 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 March 9, 2025 15:41 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2303 March 9, 2025 18:27 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 March 9, 2025 18:27 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2303 March 9, 2025 18:30 Abandoned
@github-actions github-actions bot requested a deployment to docs-2303 March 9, 2025 18:30 Abandoned
@@ -785,7 +798,7 @@ export default defineComponent({
const regexToRemoveWidget = /([?&])((chartIndex|chartGroupIndex)=\d+)/g;
return url.replace(regexToRemoveWidget, '');
},
getRepo(repo: Array<Repo>): Array<Repo> {
getRepo(repo: Array<User>): Array<User> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any particular reason to change the typing here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, following the call stack, the previous Repo type was wrong and should be User instead.

Naming was very confusing to begin with, maybe we can fix this in another PR for refactoring and cleanup. I'm worried changing parts of it now may make it even more confusing.

Copy link
Contributor

Choose a reason for hiding this comment

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

I see, maybe we should create another PR to handle this issue.

Copy link
Contributor

@CYX22222003 CYX22222003 left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Display time periods for each repository
3 participants