feat(core): support for reporting dynamic task parameters #2380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this way masked values can be detected as a special case and we can avoid leaking secrets when producing a parameterised description of an activity Related tickets: re #2223
jan-molak
force-pushed
the
features/task-parameter-reporting
branch
from
76c18f0
to
04a9f17
Compare
…ptions of Activities `description` is a new tag function that interprets the provided template literal to generate a question which could be then used to describe any parameterised activities (tasks and interactions) Related tickets: re #2223
Related tickets: re #2223
…sing Questions this allows the description to by determined dynamically when the activity is performed, and include the actual value of any Answerable parameters passed to the description in the test execution report Related tickets: re #2223
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notable changes:
Masked.valueOf(..)is now a standalone class so that it can be detected as a special case when producing a parameterised description of a taskRE: #2223
Outstanding:
Masked.valueOf(..)toMaskedValue.of(..)so that it can be used as aMetaQuestion. This would require introducing a temporary/deprecated aliasMasked.valueOf(..)to avoid breaking backwards compatibility