[Feature] Add optional parameter 'data' to execute_custom_step keyword#1
Open
osedlbauer wants to merge 1 commit into
Open
[Feature] Add optional parameter 'data' to execute_custom_step keyword#1osedlbauer wants to merge 1 commit into
osedlbauer wants to merge 1 commit into
Conversation
Add an optional parameter 'data' to the 'Execute Custom Step' keyword. This allows custom templates to access user-provided data. Signed-off-by: Oliver Sedlbauer <os@dev.tdt.de>
This file contains hidden or 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
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.
I stumbled across this project and think it is really great. It works like a charm!
This PR adds an optional parameter 'data' to the 'Execute Custom Step' keyword.
The object is passed through to the Jinja2 template, allowing custom templates to handle more complex and dynamic dialog windows.
This is a small example of the use case this PR solves:
templates/complexform.html
{% extends "dialogs/layout.html" %} {% block dialog_content %} <h5>Enter Data</h5> <form method="POST" action="/dialog/submit"> {% for key, value in data.items() %} <div class="mb-3"> <label class="form-label">{{ key }}</label> <input type="text" class="form-control" name="{{ key }}" value="{{ value }}"> </div> {% endfor %} <button type="submit" class="btn btn-primary">Submit</button> </form> {% endblock %}test.robot