Enhance the export preset interface method #102046
Open
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
fire
changed the title
citizenll
force-pushed
the
export-preset-enhancements
branch
from
c564474 to
a2d08c5
Compare
citizenll
force-pushed
the
export-preset-enhancements
branch
from
a2d08c5 to
1ca1e3b
Compare
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.
The current ExportPrset interface has limitations for custom export plugins, making it difficult to handle pck processing flexibly. This PR will expose more internal interfaces to the user layer, enhancing the plugin's processing capabilities.
My use case involves exporting different pck files based on the file list I configure during the export process.