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 JS expression for chart label typo #30

Merged
merged 21 commits into from
Nov 23, 2023
Merged

Fix JS expression for chart label typo #30

merged 21 commits into from
Nov 23, 2023

Conversation

mkrecek234
Copy link
Contributor

@mkrecek234 mkrecek234 commented Nov 21, 2023

Variables in JS expression not processed due to EOF string definition

Effect: Tooltips are no longer working as originally intended.
How to test: Open the demos/index.php and check if tooltips work on all the charts. Also there should not be a JS console error as previously an invalid parameter is passed to minimumFractionDigits

@mkrecek234
Copy link
Contributor Author

Bug was introduced by ae3b360 @mvorisek can you help fixing it, please?

@mkrecek234 mkrecek234 requested a review from mvorisek November 21, 2023 15:46
@mvorisek mvorisek added the bug label Nov 21, 2023
@mvorisek mvorisek changed the title Bug creating JS expression Fix JS expression for chart label typo Nov 21, 2023
Copy link
Member

@mvorisek mvorisek left a comment

Choose a reason for hiding this comment

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

The ae3b360 you referred has more places with such bug! Michael, always check this when doing changes!

@mvorisek
Copy link
Member

Michael, again, the PR is still not fixing all issues, see src/ScatterChart.php! Your workflow must be to identify as much as places with the possibly same issues, so all places are really fixed, ideally even cross repo, even in commented code (and as comments are not checked by cs fixer/phpstan, that is why we keep it to minimum).

@mkrecek234
Copy link
Contributor Author

@mvorisek Can you please stop teaching me what my workflow has to include? I am fixing a bug that was introduced by you which basically results from your own workflow not checking your own code changes sufficiently and introducing in this case new bugs across several scripts. I am assuming this is a joint open-source effort where people are investing their personal time and not an environment for blaming people for not matching your personal quality standards which in this case you have not met yourself. Thank you.

@mvorisek
Copy link
Member

Michael, thank you for the feedback. I was written in that way to stress that I very often feel/felt that you was opening PRs with low efford invested shifting the efford on me. Efford in fixing one line instead of fixing all cases, missing tests... Is this feedback from me clear or what can I do better?

Yes, the issue was introduced by me. Of course sorry, it slipped thru my review :)

Copy link
Contributor Author

@mkrecek234 mkrecek234 left a comment

Choose a reason for hiding this comment

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

Done.

@mvorisek mvorisek marked this pull request as draft November 22, 2023 08:03
label += ": ";
}
return label + (value ? Number(value).toLocaleString(undefined, {minimumFractionDigits: [], maximumFractionDigits: []}) : "No Data");
EOF.
Copy link
Member

Choose a reason for hiding this comment

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

dot? do not fix it, I am on this PR now...

@mvorisek mvorisek marked this pull request as ready for review November 22, 2023 11:09
@mvorisek
Copy link
Member

The changes should be good now, but I have no test env setup for this repo, I would be happy if someone else can review this PR as well.

@mvorisek mvorisek merged commit 5148d0a into develop Nov 23, 2023
@mvorisek mvorisek deleted the fix/jstooltip_bug branch November 23, 2023 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants