We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the Gitlab formatter, the full path to the composer.json file is used, which is reported to the interface.
composer.json
When clicking the link, you will get a notification that the file does not exist in the repository:
This might also be an issue with the Github formatter, which is the only other formatter to use the $composerJsonPath param.
$composerJsonPath
I believe this path should be relative to the execution dir. What do you think?
The text was updated successfully, but these errors were encountered:
It looks like this actually also causes the reported finding to be incorrect, as that seems to compare the full item including the full path.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
When using the Gitlab formatter, the full path to the
composer.json
file is used, which is reported to the interface.When clicking the link, you will get a notification that the file does not exist in the repository:
This might also be an issue with the Github formatter, which is the only other formatter to use the
$composerJsonPath
param.I believe this path should be relative to the execution dir. What do you think?
The text was updated successfully, but these errors were encountered: