Clarify PCK path argument in PCKPacker.pck_start
#97286
Merged
+10
−10
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 pck_start() function description was somewhat misleading, and lead to some confusion until I (with some help) figured out that the pck_name argument actually represents the entire file path for the .pck file.
Changed "with the name
pck_name
" to "at the file pathpck_name
" so that the description is more clear, and should not lead to any confusion as to where the .pck file is output.