-
-
Notifications
You must be signed in to change notification settings - Fork 22k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify PCK path argument in PCKPacker.pck_start
#97286
Conversation
PCKPacker.pck_start
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked the source code and I can confirm the reasoning to be correct.
Note that for the related function add_file
, the parameter is exposed as pck_path
, and that internally the parameter is actually called p_file
. If possible, we should be renaming the exposed parameter. It may have been an oversight.
I also noted the source code differences, but I didn't want to modify that since I'm not super confident in my C++ quite yet. |
PCKPacker.pck_start
PCKPacker.pck_start
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
I went ahead and changed the name of the argument too to be clearer, as |
Thanks! And congrats for your first merged Godot contribution 🎉 |
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.