You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a plugin (such as jupyfmt, several reporters output links to a non-existing page.
E.g. the text reporter:
Results of jupyfmt linter (version 0.5.1)
See documentation on https://megalinter.github.io/descriptors/jupyter_jupyfmt/
and the console reporter:
- Using [jupyfmt v0.31.0] https://megalinter.github.io/v5/descriptors/jupyter_jupyfmt
To Reproduce
Steps to reproduce the behavior:
Create a minimal setup:
cd$(mktemp -d -t mcve-XXXXXXXXXX)
cat > .mega-linter.yaml <<EOFPLUGINS: - https://raw.githubusercontent.com/kpj/jupyfmt/master/mega-linter-plugin-jupyfmt/jupyfmt.megalinter-descriptor.ymlENABLE: - JUPYTEREOF
touch dummy.ipynb # so the linter has something to run against
Run npx mega-linter-runner
The console output will include:
### Processed [JUPYTER] files
- Using [jupyfmt v0.5.1] https://megalinter.github.io/v5/descriptors/jupyter_jupyfmt
and in report/linters_logs/WARNING-JUPYTER_JUPYFMT.log:
Results of jupyfmt linter (version 0.5.1)
See documentation on https://megalinter.github.io/descriptors/jupyter_jupyfmt/
Expected behavior
Either no documentation URL should be shown, or it should be possible for the plugin to define a URL, with a possible fallback to the linter_url value.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using a plugin (such as jupyfmt, several reporters output links to a non-existing page.
E.g. the text reporter:
and the console reporter:
To Reproduce
Steps to reproduce the behavior:
Create a minimal setup:
Run
npx mega-linter-runner
The console output will include:
and in
report/linters_logs/WARNING-JUPYTER_JUPYFMT.log
:Expected behavior
Either no documentation URL should be shown, or it should be possible for the plugin to define a URL, with a possible fallback to the
linter_url
value.The text was updated successfully, but these errors were encountered: