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

Setting for different platform #23

Closed
aurexav opened this issue Jan 24, 2025 · 3 comments
Closed

Setting for different platform #23

aurexav opened this issue Jan 24, 2025 · 3 comments

Comments

@aurexav
Copy link

aurexav commented Jan 24, 2025

VSCode should ideally support this feature natively, but it hasn’t been fully implemented yet.

Introducing specific changes for one platform could potentially disrupt functionality on others.

It would be great to have a field like "custom-ui-style.external.imports.$PLATFORM" to address this.

// Currently, I have to do this every time.
{
    "custom-ui-style.electron": {
        // macOS.
        "opacity": 0.8,
        // Windows.
        // "opacity": 0.9,
        ..
    },
    "custom-ui-style.external.imports": [
        // macOS.
        "file:///Users/xavier/.vscode-insiders/extensions/brandonkirbyson.vscode-animations-2.0.7/dist/updateHandler.js",
        // Windows.
        "file:///c:/Users/x/.vscode/extensions/brandonkirbyson.vscode-animations-2.0.7/dist/updateHandler.js"
        ..
    ]
}
@subframe7536
Copy link
Owner

How about environment variable? For custom-ui-style.external.imports, the env variable is supported: ${env:YOUR_ENV_VAR:optional_default_value}.

@aurexav
Copy link
Author

aurexav commented Jan 24, 2025

I'm not sure about that. I have no experience with the ENV config. But if this makes things easier, I'd like to have a try.

What I thought is I can put the common settings into custom-ui-style.*, and the specific setting into custom-ui-style.*.$PLATFORM.

@aurexav
Copy link
Author

aurexav commented Jan 24, 2025

Use VSCode profile feature.

@aurexav aurexav closed this as completed Jan 24, 2025
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

No branches or pull requests

2 participants