The comparisons API now allows the users to update the value of the criteria scores one by one. This will allow users to rate the criteria one by one from the mobile UI of the front end.
The ComparisonCriteriaScore model now contains the score_max, representing the maximum absolute value accepted for a score. The mobile UI of the front end will submit scores with a score_max of 2, while the sliders use a score_max of 10.
I suppose that the score_max will make the constant COMPARISON_MAX deprecated. At the time of writing the constant is used by the class MehestanParameters, and by the view ScoreInconsistencies. I haven't updated these classes.
Checklist
[x] I added the related issue(s) id in the related issues section (if any)
if not, delete the related issues section
[x] I described my changes and my decisions in the PR description
[x] I read the development guidelines of the CONTRIBUTING.md
[x] The tests pass and have been updated if relevant
related issues #1940
Description
The comparisons API now allows the users to update the value of the criteria scores one by one. This will allow users to rate the criteria one by one from the mobile UI of the front end.
The
ComparisonCriteriaScoremodel now contains thescore_max, representing the maximum absolute value accepted for a score. The mobile UI of the front end will submit scores with ascore_maxof 2, while the sliders use ascore_maxof 10.I suppose that the
score_maxwill make the constantCOMPARISON_MAXdeprecated. At the time of writing the constant is used by the classMehestanParameters, and by the viewScoreInconsistencies. I haven't updated these classes.Checklist