-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Adding clickable editorUrl
from codeception.yml
#6261
Conversation
Closes Codeception#6259 I followed the syntax of https://phpstan.org/user-guide/output-format#opening-file-in-an-editor even though we would need the second `%` here. (This is due to some phpstan internals, the code ultimately reads `\str_replace(['%file%', '%line%'], ...` But I'd say having an *identical* `editorUrl` syntax between Codeception and phpstan by far outweighs the "cost" of some unneeded `%` characters... ;-)
@ThomasLandauer Could you document it in https://github.com/Codeception/codeception.github.com/blob/master/docs/reference/Configuration.md ? |
@Naktibalda Just noticed that all other config options are |
I released it yesterday, but nobody will notice if we rename it quickly, right? |
I raised #6303 |
Renamed and released as 4.1.27 |
|
Closes #6259
I followed the syntax of https://phpstan.org/user-guide/output-format#opening-file-in-an-editor even though we wouldn't need the second
%
here. (This is due to some phpstan internals, the code ultimately reads\str_replace(['%file%', '%line%'], ...
).But I'd say having an identical
editorUrl
syntax between Codeception and phpstan by far outweighs the "cost" of some unneeded%
characters... ;-)$line = 0;
is a fallback in case the trace iteration doesn't work out. I'm guessing that putting 1 for the line is better than leaving it empty.