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

Granularity of static errors #333

Closed
xml-project opened this Issue Mar 17, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@xml-project
Contributor

xml-project commented Mar 17, 2018

From a discussion with @ndw
We have a lot of static errors for special cases, but no generic error "your pipeline doesn't conform to the grammar of pipelines".

As a general rule we might say, that we want an error code for this generic error which is raised every time a pipeline violates the RNC-grammar. It is then up to the implementation to provide some useful hint what went wrong. For non-grammar errors (e.g. double port names) we will still need specific error codes.

As a result of this strategy we could reduce the number of static errors and make the specs more editable because we would not have a grammar expression AND a code anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment