We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
All the run APIs that currently accept ut_varchar2_list (specially for suitepath) should accept a comma or newline lists.
run
ut_varchar2_list
suitepath
This will greatly simplify calls from user-perspective as they don't need to remember to use ut_varchar2_list. So instead of calling:
exec ut.run(ut_varchar2_list('first','another'));
They could call:
exec ut.run('first,another');
or:
exec ut.run('first another');
exec ut.run('first, another');
This enchancement needs detrailed scoping:
We could probably remove calls that use ut_varchar2_list in release 4, as it's a breaking change.
We should indiate (Somehow) that those are depreciated
The text was updated successfully, but these errors were encountered:
Comma separated list would be sufficient for now I suppose. I'm changing the title of the issue to match this.
Sorry, something went wrong.
lwasylow
No branches or pull requests
All the
run
APIs that currently acceptut_varchar2_list
(specially forsuitepath
) should accept a comma or newline lists.This will greatly simplify calls from user-perspective as they don't need to remember to use
ut_varchar2_list
.So instead of calling:
They could call:
or:
or:
This enchancement needs detrailed scoping:
We could probably remove calls that use
ut_varchar2_list
in release 4, as it's a breaking change.We should indiate (Somehow) that those are depreciated
The text was updated successfully, but these errors were encountered: