Skip to content

Fix custom integration path validation for certain executables on Windows#19223

Merged
sergiou87 merged 2 commits intodevelopmentfrom
custom-shell-stat-fix
Sep 9, 2024
Merged

Fix custom integration path validation for certain executables on Windows#19223
sergiou87 merged 2 commits intodevelopmentfrom
custom-shell-stat-fix

Conversation

@sergiou87
Copy link
Member

@sergiou87 sergiou87 commented Sep 9, 2024

Closes #19217

Description

It seems some executables on Windows throw an EACESS error when trying to stat them, but Desktop is still able to open them.

The previous logic used stat to determine if the path points to a file or a directory. However, for executables I think we can get away with just using access, and then on macOS we can still leverage stat to check if it points to a directory before trying to get its bundle ID.

Release notes

Notes: [Fixed] Allow choosing certain Windows executables as custom editor or shell

Copy link
Contributor

@tidy-dev tidy-dev left a comment

Choose a reason for hiding this comment

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

✨ Looks good.

@sergiou87 sergiou87 merged commit 14b9133 into development Sep 9, 2024
@sergiou87 sergiou87 deleted the custom-shell-stat-fix branch September 9, 2024 15:20
sergiou87 added a commit that referenced this pull request Sep 9, 2024
Fix custom integration path validation for certain executables on Windows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The new integrations feature doesn't work for some paths?

2 participants