Skip to content
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

0086a-imports-input #280

Closed
wants to merge 1 commit into from

Conversation

StrayAlien
Copy link
Contributor

An import input data test to cover what is discussed over here: #274.

This suite is pretty compact - it is actually only one test. It has three models A, B and C. A imports B as 'i', and B imports C as 'i'. A also imports C directly as 'x'.

A has a decision that uses a local inputData and also the a decision/inputData from B. That decision in B also uses a 'local' inputData and the a decision/inputData in C. The decision in C uses a 'local' inputData.

The decision in A also uses the decision/inputData and decision from C directly.

The inputNode to the test is structured to support that.

Phew.

@agilepro
Copy link
Contributor

agilepro commented Apr 5, 2019

Matteo to double check and merge if it all looks OK.

@StrayAlien
Copy link
Contributor Author

@tarilabs - you were saying you prefer 'context' objects rather than dot-path notation for the data - is that how Red Hat implements it .. or do you do dot-notation?

(I prefer an object - it is easy and unambiguous in terms of naming)

@StrayAlien StrayAlien closed this May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants