Recursive model references causes error during generation #243
Comments
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jun 16, 2016
…ck_dotproject_for_tutorial_example to development * commit '30e276545814b98042621af45c9f395d07ac1075': update mapping example by moving mapping file to folder "src/mappings" add back .project file to tutorial examples
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jul 7, 2016
Signed-off-by: Erle Czar Mantos <[email protected]>
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jul 7, 2016
Signed-off-by: Erle Czar Mantos <[email protected]>
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jul 7, 2016
Signed-off-by: Erle Czar Mantos <[email protected]>
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jul 7, 2016
…ing generation Signed-off-by: Erle Czar Mantos <[email protected]>
erlemantos
pushed a commit
to bosch-io/vorto
that referenced
this issue
Jul 11, 2016
…tes suggestions by Alex to not make the 'generator menu' disappear but clicking it when an error is present will make it throw out an error in the console. Signed-off-by: Erle Czar Mantos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a user uses model A inside model A and invokes a code generator, a stack overflow error occurs.
In order to circumvent this issue, the model editor should not allow to use a model recursively resulting in a validation error.
Validation Error occurs on:
Model A --> Model A
Model A --> Model B --> Model A
The text was updated successfully, but these errors were encountered: