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

Fix heatmap first color being unused #22158

Merged
merged 3 commits into from
Dec 18, 2022

Conversation

silverwind
Copy link
Member

Backport #22157. vue3-calendar-heatmap has the behaviour that the first and second colors are mapped to values null and 0, meaning the second color was not used as intended for values > 0. I think this is a behaviour change from previous vue2 version that was missed during the upgrade.

This change makes first and second values the same, so the heatmap can now use one additional color for meaningful values.

vue3-calendar-heatmap has the behaviour that the first and second colors
are mapped to values null and 0, meaning the second color was not used
as intended for values > 0. I think this is a behaviour change from
previous vue2 version that was missed during the upgrade.

This change makes first and second values the same, so the heatmap can
now use one additional color for meaningful values.
@silverwind silverwind added this to the 1.18.0 milestone Dec 18, 2022
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Dec 18, 2022
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Dec 18, 2022
Comment on lines +31 to 32
'var(--color-secondary-alpha-70)',
'var(--color-secondary-alpha-70)',
Copy link
Member

Choose a reason for hiding this comment

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

We should probably mention why we do the same thing twice here…

Copy link
Member Author

Choose a reason for hiding this comment

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

Don't really feel like littering the code too much with info that can be obtained by reading the module's docs:

The color at rangeColor[0] will always represent the values for a count: null
The color at rangeColor[1] will always represent the values for a count: 0

@lafriks lafriks merged commit e88218f into go-gitea:release/v1.18 Dec 18, 2022
@silverwind silverwind deleted the backport-22157 branch December 18, 2022 19:33
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants