-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Issue344 RA schema extension #353
base: develop
Are you sure you want to change the base?
Issue344 RA schema extension #353
Conversation
Hello @xofolowski! Thank you for your continuous contribution!
Could you please confirm that it will work with the current confluence jinja templates? |
…atc-react into issue344_RA-schema-extension
Hi @yugoslavskiy, |
Hi @yugoslavskiy, |
Hello @xofolowski ! Thank you very much for your contribution! Sorry for the delayed reply — having extremely busy time. Will check it it up shortly (: |
|
||
{% if workflow is defined and workflow|length %} | ||
## Workflow | ||
**Please note:** This RA has not yet been converted to the extensible RA scheme |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xofolowski could you please tell me if this comment is still actual?
@xofolowski could you please restore |
As discussed in Slack channel and Issue 344, I thought it might be useful to have an extensible / customisable yml-schema for response activities.
Basically, a new array "details" was introduced, that can contain arbitrary variables (including additional arrays).
In RA_1000_testing.yml I am showing, how the result could look like.
Actually, it's not a huge change but grants much more flexibility. Backward compatibility is granted.
As of now, appropriate jinja2-templates have only been created for MD.