fix: only use og:image if http or https url #75
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Does a few small changes.
I decided not to base64 encode/inline the favicon when it's a
file://protocol URL:file://for absolute URLs. (Though it wouldn't be hard to tack on support for relative.)resume.jsonfile, though this is unintuitive.)I figured until someone comes forward to complain about it otherwise, I'll refrain from taking any action here. I'll skip the
og:imagewhen it's not an HTTP url, otherwise we'll just inline it into the document exactly at the user provided and assume they know what they're doing.Related
basics.imageresolves to a file that exists, base64 encode and inline it #30Summary by CodeRabbit
Bug Fixes
Improvements
Tests