Is it possible to configure the extension to enable a non-default package trait

[tachyonics]

At the moment I am trying to develop a package with a package trait. If I make this trait enabled by default everything works as expected - its dependencies show up in the sidecar and code completion within any conditional code works as expected.

However if I make the trait not enabled by default, I haven't been able to configure the extension to temporarily enable it for development. I attempted to set .sourcekit-lsp/config.json as

{
    "swiftPM": {
        "traits": ["DynamoDB"]
    }
}

as per https://github.com/swiftlang/sourcekit-lsp/blob/main/Documentation/Configuration%20File.md but this didn't have any effect (the extension treats the trait as disabled). Is there any way to enable this temporarily for development?

[plemarquand]

You can configure traits for development by configuring the swift.packageArguments setting in your .vscode/settings.json. For instance: "swift.packageArguments": ["--traits", "DynamoDB"]

This setting configures extra arguments to pass to swift commands that do package resolution.

You'll also want to keep the .sourcekit-lsp/config.json setting you already have to ensure sourcekit-lsp performs indexing with the correct traits enabled.

[adam-fowler]

You can configure traits for development by configuring the swift.packageArguments setting in your .vscode/settings.json. For instance: "swift.packageArguments": ["--traits", "DynamoDB"]

This setting configures extra arguments to pass to swift commands that do package resolution.

You'll also want to keep the .sourcekit-lsp/config.json setting you already have to ensure sourcekit-lsp performs indexing with the correct traits enabled.

Would you also need to add this to the build arguments?

[plemarquand]

@adam-fowler swift.packageArguments applies to any command that may do package resolution, so they'll be added to swift build and swift test automatically in addition to swift package resolve/swift package update

[plemarquand]

I think it would be nice to have some mechanism to set this on a per-launch target basis though, so instead of having to toggle traits 'globally' in settings you can have different launch configs that build/run with different traits.