Add a more powerful postprocessor script #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I also didn't change the previous postprocessor, but using assert for use cases like this is unideal, since it's really just meant for development and can get stripped away in prod. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I wrote a more powerful script for computing a bounding box and cropping. My new script requires passing
-cto reSnap, and there currently isn't a way to add extra args, to get the best effect. This is because reSnap automatically does some color adjustments that are very lossy. I'm working on rewriting the plugin to some extent to conform to the newer obsidian API and clean things up a bit, and I'll add the ability to specify arguments.