@volkovs I just wondering: why are you still using this branch?

1.4.24 seems usable enough and doesn't require so much efforts to upgrade.

@just-boris please correct me if I am wrong, but 1.4.24-SNAPSHOT in master branch has new face -> client side of allure plugins (I mean custom ones) is not backward compatible.

All changes in Java part were rolled back, so now new face is a drop-in replacement.

Even more, I got the bug report about number rounding and fixed it there several weeks ago

@just-boris Yes, exactly, I was "cherry-picking" it from your commit. The issue is that new face is a breaking change for custom plugin providers.

So, we hope you might release 1.4.x branch with this fix (before we rewrite our plugins for new face).

@volkovs thanks for the explanation, then it really needs to be merged.

Hope @baev will do this, when he will get an access to internet

@baev Hi, do you think you could release 1.4.x branch (old face) with this fix?

@volkovs oh, sorry, kinda forget about it. I'll fix this ASAP

test this please

SonarQube analysis reported 3 issues:

• 2 major
• 1 minor

Watch the comments in this conversation to review them.
Note: the following issues could not be reported as comments because they are located on lines that are not displayed in this pull request:

• This function has 141 lines, which is greater than the 100 lines authorized. Split it into smaller functions.
• Function has a complexity of 26 which is greater than 10 authorized.
• Rename this 'PieChart' function to match the regular expression ^[a-z][a-zA-Z0-9]*$

@baev No hurry. Take your time. Thanks.

@volkovs done https://github.com/allure-framework/allure-core/releases/tag/allure-core-1.4.23.HOTFIX1

@baev thank you very much