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

Introduce better string replacement #557

Open
tyBouch opened this issue Jul 12, 2023 · 0 comments · May be fixed by #558
Open

Introduce better string replacement #557

tyBouch opened this issue Jul 12, 2023 · 0 comments · May be fixed by #558
Assignees

Comments

@tyBouch
Copy link
Collaborator

tyBouch commented Jul 12, 2023

As it stands our string replacement support for variables is split into two differing calls:
replaceVariable()
and
replaceStoredVariables()

These function slightly different in that one supports testdata. The other does not. This causes issues in items such as API where you cannot use testdata or yml configurations to load dynamic constructed API paths.

As a user I would like these combined with the following load priority:
-Locally set by test or configuration
-Yml file
-Original text if not found

@tyBouch tyBouch self-assigned this Jul 12, 2023
@tyBouch tyBouch linked a pull request Jul 13, 2023 that will close this issue
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 a pull request may close this issue.

1 participant