Merged
Conversation
AUTOMATIC1111
approved these changes
Jul 30, 2023
This was referenced Jul 30, 2023
Closed
4 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
fix issue #12149 introduced by PR #11747
instead of having a dedicated image saving sequence just reuse everything
should make maintain easier
since the image save file name is parsed by
FilenameGeneratorit could cause potential issues if they are special sequences in the file nameI have mentioned past that we shouldn't use valid file name characters for as pattern (square brackets
[xxx])I propose we switch to using
<xxx>it should be possible to make the transition without breaking change
Checklist: