-
Notifications
You must be signed in to change notification settings - Fork 50
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
Introduce dynamic manual instructions by value setting from transformation context #233
Comments
@fabiocarvalho777 Few observations here.
Apart from the above points, what is your take on validation of placeholders at the time of creation. From the above requirement, it does not seem like there is a limit on creating a placeholder by TU. This means that there might arise a situation where replication of placeholders could happen. In such a case, what should be the responsibility of One more point. How about allowing Let me know your thoughts on the above-mentioned points. |
@amriteya see my answers below: First bullet
Assuming when you say "manual instruction" you mean the document MD file, that is correct. Second bulletFeel free to change the implementation as needed, as long as the overall functionality is preserved and contracts are respected. Bullet threeDuring transformation time, validate this way:
Definition time attributes validationDuring definition time, It should check for Using a map to specify attributesI can see that being helpful in very few cases. I believe in most of the cases a regular |
@fabiocarvalho777 - is there any plan to implement this feature in the near future ? |
Currently every manual instruction document is static. Allow the usage of transformation context attributes to set portions of manual instruction document via interpolation, by replacing placeholders in the document with values from transformation context attributes.
API changes
Notice the
addAtribute
method call. The first parameter,"appName"
, is the placeholder key in the document text, to be replaced by the value of the specified transformation context attribute (the second parameter).The text was updated successfully, but these errors were encountered: