You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: Currently the vote or election results have a fix number of decimal places. This should be improved.
What is needed:
A new setting per meeting should be integrated in the motion menu, which grants the admin the possibility to configure the amount of decimal places. The setting should be set for all results and NOT configurable per single vote/election.
Open question: How much digits should be available as option.
The text was updated successfully, but these errors were encountered:
MSoeb
changed the title
Vote/election results: integrate new function for decimal places
Vote/election results: integrate new function to configure amount of decimal places
Nov 3, 2023
The backend currently only supports exactly 6 decimal places. No variability, especially no dynamic changes in the running application.
If this is to be reflected in the backend, it would require profound changes to the system. While that wouldn't necessarily be a bad thing and may prove to be practical in the long run, it would require a lot of planning and we should ask ourselves if this issue is worth that effort.
Alternative:
When we limit the setting to only accept the numbers 0-6, it would probably be possible to change the client so that it rounds the actual number to the correct amount of decimal places, the real decimal values would still be present in the backend though.
Description: Currently the vote or election results have a fix number of decimal places. This should be improved.
What is needed:
A new setting per meeting should be integrated in the motion menu, which grants the admin the possibility to configure the amount of decimal places. The setting should be set for all results and NOT configurable per single vote/election.
Open question: How much digits should be available as option.
The text was updated successfully, but these errors were encountered: