Skip to content
This repository has been archived by the owner on Nov 20, 2024. It is now read-only.

Configuration validation #75

Open
steveworley opened this issue Oct 24, 2016 · 0 comments
Open

Configuration validation #75

steveworley opened this issue Oct 24, 2016 · 0 comments

Comments

@steveworley
Copy link
Collaborator

The edit/add form should have validation to prevent bad configuration values as misconfiguration can cause memory leaks and prevent pages from loading.

Example:

X Tick Values: 2010-11, 2011-12, 2012-13, 2013-14

The description states only numeric values are supported but it is not clear that 2010-11 is not a numeric value and can lead to some confusion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant