-
Notifications
You must be signed in to change notification settings - Fork 1
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
Incorrect generation while specifying an output-dir without a trailing slash #7
Comments
Farigh
added a commit
that referenced
this issue
Jul 29, 2020
Passing a path without an ending slash could result in incorrect index.html generation. If the provided path does not end with a slash, it's now added. --- Added the related `relative_path_report` test to the `generate_html_outputs` test-suite. This test-suite tests both relative paths and non-slash ending paths as parameter values. The special "." and ".." values are tested as well. --- This commit fixes #7
Farigh
added a commit
that referenced
this issue
Jul 29, 2020
Passing a path without an ending slash could result in incorrect index.html generation. If the provided path does not end with a slash, it's now added. --- Added the following related tests to the `generate_html_outputs` test-suite: - relative_path_report(relative_path) - relative_path_report(relative_path_no_leading_slash) - relative_path_report(current_dir_in_path) - relative_path_report(current_dir_in_path_no_leading_slash) - relative_path_report(current_dir_out_path) - relative_path_report(current_dir_out_path_no_leading_slash) This test-suite covers both relative paths and non-slash ending paths as parameter values. The special "." and ".." values are tested as well. --- This commit fixes #7
Farigh
added a commit
that referenced
this issue
Jul 29, 2020
Passing a path without an ending slash could result in incorrect index.html generation. If the provided path does not end with a slash, it's now added. --- Added the following related tests to the `generate_html_outputs` test-suite: - relative_path_report(relative_path) - relative_path_report(relative_path_no_leading_slash) - relative_path_report(current_dir_in_path) - relative_path_report(current_dir_in_path_no_leading_slash) - relative_path_report(current_dir_out_path) - relative_path_report(current_dir_out_path_no_leading_slash) This test-suite covers both relative paths and non-slash ending paths as parameter values. The special "." and ".." values are tested as well. --- This commit fixes #7
Farigh
added a commit
that referenced
this issue
Jul 29, 2020
Passing a path without an ending slash could result in incorrect index.html generation. If the provided path does not end with a slash, it's now added. --- Added the following related tests to the `generate_html_outputs` test-suite: - relative_path_report(relative_path) - relative_path_report(relative_path_no_leading_slash) - relative_path_report(current_dir_in_path) - relative_path_report(current_dir_in_path_no_leading_slash) - relative_path_report(current_dir_out_path) - relative_path_report(current_dir_out_path_no_leading_slash) This test-suite covers both relative paths and non-slash ending paths as parameter values. The special "." and ".." values are tested as well. --- This commit fixes #7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While using
generate_html_report.sh
with--output-dir=. --input-dir=report
, the resulting output is as follows:expected output:
The index.html content is not correct either:
expected:
Note: Using
--output-dir=./
works fineThe text was updated successfully, but these errors were encountered: