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

PyCharm: Do NOT overwrite arguments from template #1070

Open
raphaelcamus opened this issue Jun 13, 2024 · 0 comments
Open

PyCharm: Do NOT overwrite arguments from template #1070

raphaelcamus opened this issue Jun 13, 2024 · 0 comments
Labels
enhancement New feature or request robotframework-ls

Comments

@raphaelcamus
Copy link

Hi,

Currently, after having modified the "Robot Framework" configuration template in PyCharm, when you run a test using the "green array", it creates a "Run: xxx" run configuration from the template, but it only keeps the "Before launch" and overwrites target, working dir, env variables and arguments.

I would like it to keep my arguments (and maybe env vars too, though I do not need it for now)

I have noticed that it is done in robotframework-intellij\src\main\java\robocorp\dap\linemarker\RobotRunAction.java

I wanted to modify line 76 with runOptions.args = args.addAll(runOptions.args);, template coming second, as from doc:

Options that are marked with an asterisk (*) can be specified multiple times.
For example, --test first --test third selects test cases with name first
and third. If an option accepts a value but is not marked with an asterisk,
the last given value has precedence. For example, --log A.html --log B.html
creates log file B.html. Options accepting no values can be disabled by
using the same option again with no prefix added or dropped. The last option
has precedence regardless of how many times options are used. For example,
--dryrun --dryrun --nodryrun --nostatusrc --statusrc would not activate the
dry-run mode and would return a normal return code.

but I can't build the plugin, not even test without any modifications (.\gradlew test fails)

Would it be possible to have this feature ? It would be more handy than using Run/Debug configurations.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request robotframework-ls
Projects
None yet
Development

No branches or pull requests

1 participant