Skip to content
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

Should we run all checks and use module selector only for front-end? #5

Open
vmdude opened this issue Aug 3, 2016 · 0 comments
Open
Assignees
Labels

Comments

@vmdude
Copy link
Member

vmdude commented Aug 3, 2016

By default, checks will be run (and so data will be retrieved) only if user enable it on the module selector.

When the user will enable some checks, data will not yet be retrieved (as it will be on the next scheduler run).
This can be misinterpreted if user visit a page between the activation of the check and the run of the scheduler, as all checks will be GREEN (aka no error as there is no data).

So we could choose to:

  • run all checks by default, and module selector will only be used for front-end render
  • find a way to separate the 'no error' from the 'no data' state
  • better inform user of this situation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants