Skip to content

fix: make non-base64 media paths relative to report location#1040

Open
decembercomposer697-hue wants to merge 1 commit into
pytest-dev:masterfrom
decembercomposer697-hue:fix/relative-media-paths
Open

fix: make non-base64 media paths relative to report location#1040
decembercomposer697-hue wants to merge 1 commit into
pytest-dev:masterfrom
decembercomposer697-hue:fix/relative-media-paths

Conversation

@decembercomposer697-hue

Copy link
Copy Markdown

Fixes #309: when extra media content is a file path (not base64),
it was used as-is in HTML, creating absolute paths. Now resolves
relative to the report's parent directory.

✅ Unit tests pass (7/7)

When extra media content is a file path (not base64), it was
previously used as-is in the HTML, creating absolute paths that
break when the report is moved. Now resolves relative to the
report's parent directory.
@decembercomposer697-hue

Copy link
Copy Markdown
Author

Hi! This PR fixes the issue where non-base64 media paths were absolute instead of relative to the report location. All unit tests pass. Would appreciate a review!

@RonnyPfannschmidt RonnyPfannschmidt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs some tests added that would fail without the change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

links generated in the html file for attachments are absolute, there is no way to make them relative

2 participants