I wonder if it might be good to make some checks on the data to make sure it conforms to expectations. Ideally, any time something does not this would be logged, or the team would receive an email or something. Another option would be do go to some sort of alert/error page when funky things happen. Perhaps a message could give a bit of an explanation of the problem and the user could be prompted to contact us if they think what they tried should actually work.
This would help catch edge cases like this during development (and possibly also once we have real users, who are likely to try combinations that have not been tested).
I wonder if it might be good to make some checks on the data to make sure it conforms to expectations. Ideally, any time something does not this would be logged, or the team would receive an email or something. Another option would be do go to some sort of alert/error page when funky things happen. Perhaps a message could give a bit of an explanation of the problem and the user could be prompted to contact us if they think what they tried should actually work.
This would help catch edge cases like this during development (and possibly also once we have real users, who are likely to try combinations that have not been tested).
Originally posted by @rpruim in https://github.com/Energy-Visualizer/eviz/issues/31#issuecomment-2177274756