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

handle hardcoded delimiters if exist in the key/values of the uft parameters #1114

Open
wants to merge 3 commits into
base: WS_2_0
Choose a base branch
from

Conversation

dCode91
Copy link

@dCode91 dCode91 commented Oct 31, 2018

  • handle comma escape in the parameters keys or values
  • add parameter for name_value delimiter

Daniel Crisan and others added 2 commits October 31, 2018 11:38
- handle comma escape in the parameters keys or values
@lrevnic
Copy link
Member

lrevnic commented Oct 31, 2018

@DanielCrisan in general we use , as default value for delimiter; what is the reason for not following the same practice here?

@dCode91
Copy link
Author

dCode91 commented Nov 1, 2018

In this use case we talk about two delimiters in the same input because parameters inputs is a list of key:value. So about the delimiter between the key and value, user should be able to change it because it can happen that the value contains ":" character. Is the same with the , delimiter for the list, user should be able to escape the , in the param value. Because , is already used for the list iteration.

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 this pull request may close these issues.

2 participants