Difference between workspace.useThirdParty and workspace.library

[TimManzi]

Wondering if the two are the same thing. Also are "ambient" definitions in /types automatically discovered or do I have to add them to workspace.library?

[carsakiller]

Hello 👋

workspace.userThirdParty is a setting that allows you to define a directory that contains many addons (previously called user libraries). Addons in the provided directory can be suggested to be enabled in a workspace if they are configured correctly and if workspace.checkThirdParty is not false.

workspace.library is a setting that allows you to specify paths to definition files. When applying a recommended addon from your workspace.userThirdParty directory, this setting is set for you.

Definition files placed in your workspace will be used, as is explained on the libraries page in the wiki. It is recommended to add a @meta annotation to the top of the files, though, so they are not treated as runtime code.

[TimManzi]

Ahh thanks. I guess the only confusion I'm left with is this bit:

When applying a recommended addon from your workspace.userThirdParty directory, this setting is set for you.

Because the docs also say that if an add-on contains definitions in its library/ folder then you must add that to workspace.library

[carsakiller]

When an addon is applied automatically using the addon manager or the prompt from an addon from the workspace.userThirdParty directory, the setting is set for you. If you are to download an addon and manually enable it, workspace.library is what you are manually setting to enable the discovery and usage of the addon's definition files.