Skip to content
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

Fix: linuxInode is saved in VS Code settings #208

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Mateusz-Grzelinski
Copy link
Collaborator

@Mateusz-Grzelinski Mateusz-Grzelinski commented Sep 29, 2024

do not squash merge.

Needs to be tested on linux, now I do not have access to linux.

@Mateusz-Grzelinski Mateusz-Grzelinski changed the title fix-temp-variable-is-saved-in-settings Fix: linuxInode is saved in VS Code settings Sep 29, 2024
src/blender_executable.ts Outdated Show resolved Hide resolved
@@ -180,6 +180,10 @@ async function getFilteredBlenderPath(type: BlenderType): Promise<BlenderPathDat
// update VScode settings
if (settingsBlenderPaths.find(data => data.path === pathData.path) === undefined) {
settingsBlenderPaths.push(pathData);
// do not save linuxInode is settings
for (const settingExe of settingsBlenderPaths) {
settingExe.linuxInode = undefined;
Copy link
Owner

Choose a reason for hiding this comment

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

Maybe it's better to explicitly mention the properties that should be stored instead of excluding some? That makes it more obvious what's going on imo.

linuxInode?: never;
}

export type BlenderExecutablesRuntime = {
Copy link
Collaborator Author

@Mateusz-Grzelinski Mateusz-Grzelinski Sep 30, 2024

Choose a reason for hiding this comment

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

what about a separate type for saving settings? unfortunately renaming made some noise

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.

2 participants