Skip to content

Clarify Windows export warnings for File and Product Version #106007

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

B-Zhen
Copy link

@B-Zhen B-Zhen commented May 2, 2025

A proposed fix for #104814 - See the comment there

Does the following

  • Fixes the File Version warning to be more specific
  • Fixes the Product Version warning to be more specific
  • Edits the file warning logic to match the new "any string starting with a number" req

Bugsquad edit:

A proposed fix for godotengine#104814 - See the comment there

Does the following

- Fixes the File Version warning to be more specific
- Fixes the Product Version warning to be more specific
- Edits the file warning logic to match the new "any string starting with a number" req
@B-Zhen B-Zhen requested a review from a team as a code owner May 2, 2025 03:44
@AThousandShips AThousandShips changed the title Clarify Windows Export Warnings (Issue 104814) Clarify Windows Export Warnings May 2, 2025
!version_array[1].is_valid_int() || !version_array[2].is_valid_int() ||
!version_array[3].is_valid_int() || product_version.contains_char('-')) {
return TTR("Invalid product version.");
if (product_version[0].is_valid_int()) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't compile:

no member named 'is_valid_int' in 'CharProxy<char32_t>'

I'm not sure how CharProxy<char32_t> works, but is_digit(production_version[0]) (from core/string/char_utils.h) may work.

@@ -388,17 +388,14 @@ String EditorExportPlatformWindows::get_export_option_warning(const EditorExport
if (version_array.size() != 4 || !version_array[0].is_valid_int() ||
!version_array[1].is_valid_int() || !version_array[2].is_valid_int() ||
!version_array[3].is_valid_int() || file_version.contains_char('-')) {
return TTR("Invalid file version.");
return TTR("Invalid file version. Proper format is x.x.x.x where x is any int.");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
return TTR("Invalid file version. Proper format is x.x.x.x where x is any int.");
return TTR("Invalid file version. The expected format is `n.n.n.n` where `n` is any integer.");

!version_array[3].is_valid_int() || product_version.contains_char('-')) {
return TTR("Invalid product version.");
if (product_version[0].is_valid_int()) {
return TTR("Invalid product version. Allowable format is any string beginning with a number");
Copy link
Member

@akien-mga akien-mga May 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
return TTR("Invalid product version. Allowable format is any string beginning with a number");
return TTR("Invalid product version. The expected format is any string starting with a number.");

@akien-mga akien-mga changed the title Clarify Windows Export Warnings Clarify Windows export warnings for File and Product Version May 2, 2025
@AThousandShips AThousandShips added this to the 4.x milestone May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unhelpful warnings in Windows export profile
3 participants