You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to configure Asciidoctor attributes at the folder level using .vscode/settings.json, the configuration is ignored.
However, the same configuration works when set in VSCode's User Settings.
Steps to reproduce
Create a .vscode/settings.json file in your repository with:
The getConfiguration method is called with null as the scope parameter.
According to VSCode API documentation, this means it will only get the global configuration.
To properly support folder-level configuration, the extension should probably use the appropriate scope (Uri or WorkspaceFolder) when calling getConfiguration.
Additional Information
VSCode Version: 1.96.2
Extension Version: 3.5.2
OS: Windows 11 on remote WSL Ubuntu 24.04
The text was updated successfully, but these errors were encountered:
Description
When trying to configure Asciidoctor attributes at the folder level using
.vscode/settings.json
, the configuration is ignored.However, the same configuration works when set in VSCode's User Settings.
Steps to reproduce
.vscode/settings.json
file in your repository with:Open an AsciiDoc file with front matter.
The front matter is still processed in the preview, indicating the attribute is not taken into account
Other folder settings (non-preview related) work correctly, confirming that the .vscode/settings.json file is properly loaded
Analysis
Looking at the extension's source code, specifically in
asciidoctorAttributesConfig.ts
:The
getConfiguration
method is called with null as the scope parameter.According to VSCode API documentation, this means it will only get the global configuration.
To properly support folder-level configuration, the extension should probably use the appropriate scope (Uri or WorkspaceFolder) when calling getConfiguration.
Additional Information
VSCode Version: 1.96.2
Extension Version: 3.5.2
OS: Windows 11 on remote WSL Ubuntu 24.04
The text was updated successfully, but these errors were encountered: