Description Kiren Pillay 2018-08-21 03:48:23 EDT

The current validation framework prevents other tasks from running until it is complete. While it is a good idea to validate files as a value add, most of the time it is unnecessary and users have to disable it to continue with their development.

While disabling it is a solution, validation does have value, and is useful to the developer. (validation errors can be reported in the errors dialog etc).

I suggest that Validation run in the background but be non-blocking. If the developer runs his code and receives and discovers and error due to validation, the code run would point it out faster than the validation process would. 

While it is running in the background, and say the developer ran his first test run, by that time the validation would hopefully have completed and the relevant markers would presented to the user.