Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

LIVE-2119 Bugfix/graph out of bound issue #2495

Merged
merged 1 commit into from
May 6, 2022

Conversation

LFBarreto
Copy link
Contributor

@LFBarreto LFBarreto commented May 6, 2022

Issue in graphs when values could be out of range due to too big of a difference between min and max Y axis values.
d3 lib would then try to create an svg area targeting out of bounds points.
A simple switch in the min value to target for the gradient area clears that

Type

Bug Fix

Context

LIVE-2119

Parts of the app affected / Test plan

…e values in svg in certain cases where the data domain values were too split in Y axis
@LFBarreto LFBarreto requested a review from a team as a code owner May 6, 2022 14:50
@LFBarreto LFBarreto requested review from a team May 6, 2022 14:50
@LFBarreto LFBarreto requested review from a team as code owners May 6, 2022 14:50
@github-actions
Copy link

github-actions bot commented May 6, 2022

Thanks for your contribution.
To be able to merge in develop branch, you need to:

  • pass the CI
  • if needed, run /generate-screenshots
  • have a dev review
  • have a QA review
  • if needed, /upgrade-llc

Why /generate-screenshots ?

If your PR contains UI related changes,
it might be necessary to regenerate screenshots.

Why /upgrade-llc ?

If your PR requires an update to the ledger-live-common library,
once the PR is merged on develop on ledger-live-common side,
you need to run /upgrade-llc to switch back to ledger-live-common@develop here before merging.

@LFBarreto LFBarreto changed the base branch from develop to release/3.1.x May 6, 2022 14:51
@LFBarreto LFBarreto merged commit dd51c39 into release/3.1.x May 6, 2022
@LFBarreto LFBarreto deleted the bugfix/graph-out-of-bound-issue branch May 6, 2022 14:57
This was referenced May 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants