-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Providing score trend on plugins #493
Comments
We just need to create a api to return a list of score with timestamp of generation, It would help the UI to analyse the trend easily |
No you don't. In the current |
Thanks @alecharp so the endpoint will be /api/scores/{pluginName} this will return all the score result |
No, that would still be a new endpoint. We want the trend to be accessible in the current |
@alecharp Thanks, in this case, we can create and pass another parameter in the score card, |
No. We want the elements of |
@alecharp Example, in single DB call ? |
Either you provide an array of previous score, or only one value. Last value is enough. |
Thank you so much @alecharp I guess it is good to provide all previous score to better analysis |
No, only last score is better. It's easier to interpret. |
Knowing the current score of a plugin great, but knowing if it improves and is getting worse would be a nice addition to the data we have on each plugin.
In addition, knowing when that previous score was computed would help understand if the plugin is change frequently or not.
The text was updated successfully, but these errors were encountered: