|Re: working around lack of project-wide validation [message #870284 is a reply to message #870262]
||Mon, 07 May 2012 15:00
| Rafael Chaves
Registered: April 2012
I think as a starting point I would make it a manual "build" that the user has to start.
It is a fair suggestion but breaks the user experience I intend. I want to have both source validation and automated tests running (asynchronously) for every save. What you suggest is a good starting point, but I am not sure I would ever be able to do better in the future. Need to think about that.
The validation server would then fetch the latest files (presumably syncing its own cache), and then run the validation.
Do you mean, syncing its cache with the git server? Or with the Orion server? I assume the latter isn't possible (Orion project contents are not available).
You could also hook into the Orion validation service to display the results within the editor page
Yeah, I was intending to use the validation service that way, based on the results from the remote compilation service.
The other option would be a client side project-wide validation, perhaps running in a web worker. Architecturally that would be much simpler, but it depends on the kind of validation you are doing (presumably if you have a large body of Java code doing the validation this isn't an option).
Yup. Compiler is behind a REST API and is implemented in Java. It is the same scenario we discussed on this forum earlier this year ("project validation in Orion").
Powered by FUDForum
. Page generated in 0.01708 seconds