Keep _export_begin()'s path argument always consistent
#81016
Merged
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
|
It seems to be |
YeldhamDev
changed the title
_export_being()'s path argument always consistent_export_begin()'s path argument always consistent
YeldhamDev
force-pushed
the
took_me_a_while_to_discover_why_my_plugin_was_acting_weird
branch
from
d6cd401
to
cc859fd
Compare
|
@akien-mga The path is given to the |
akien-mga
approved these changes
Aug 27, 2023
|
Thanks! |
YeldhamDev
deleted the
took_me_a_while_to_discover_why_my_plugin_was_acting_weird
branch
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.
Currently, the
pathargument given by_export_begin()will show a simplified path if exporting a single preset, or an absolute one if exporting them all at once. This PR makes sure that in both cases the simplified one is given.