-
Notifications
You must be signed in to change notification settings - Fork 4
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
Xtext tool doesn't report back editor-generation errors #39
Comments
@szschaler does the included support in commit e3f041d for displaying stderr in the log resolve this? or is something more required here? Could you provide an example of the kind of error in the Xtext activity file that isn't seen? |
Sorry, haven't had time to check myself yet. Anything where the grammar isn't valid would be relevant here. For example, a grammar that defines a top rule, but then references an empty rule:
This should produce an error message from the generation process so that the student can work out what went wrong. |
Almost works now, but we have lost the presentation of the error notification to students when something goes wrong. |
When something goes wrong when generating an editor from the Xtext tool, the student cannot see the Xtext error message because this isn't reported back to the platform. Instead, all they see is a generic error message that there was an issue generating the editor.
The text was updated successfully, but these errors were encountered: