Hey, @Eris, as of now, the package author has corrected the issues you've mentioned, we encourage you to turn the review to a thread, or change the rating to neutral, as it no longer reflects the current state of the package
Of course, you are free to ignore this message and maintain your review, current policy is to turn outdated bug reports to threads, so this review kinda falls in a gray area (since it's wasn't really a "bug")
See title.
Can you elaborate
i beleive the context is this from the orginal long description
Yes, thanks for looking into this.
sorry, i had no idea this was a content rule. updating now
is that better?
Hey, @Eris, as of now, the package author has corrected the issues you've mentioned, we encourage you to turn the review to a thread, or change the rating to neutral, as it no longer reflects the current state of the package
Of course, you are free to ignore this message and maintain your review, current policy is to turn outdated bug reports to threads, so this review kinda falls in a gray area (since it's wasn't really a "bug")
converted review into a thread
Oh, I just wanted to make people aware of the actions (I assume in bad faith) of the author; thanks for the suggestions.
You were right to shine a light on the issue :)
We have cleared up there was no malicious intent so we hope this won't happen again
i will make sure it wont happen again, apologies.