Repository navigation
Description of preferredPathSeparator setting is incorrect #12597
Description
Environment
(irrelevant)
Bug Summary and Steps to Reproduce
We have a setting that supposedly controls the slash behavior for #include auto complete:
The setting description states that it is supposed to be the character used for path separators in the auto complete results. However, it doesn't appear that we add any separators for #include auto complete. I thought that we used to, but now it seems the setting is only used for paths returned via the code actions. I believe this setting was intended to cover more than just the #include auto complete case, but for now, I think we need to restore the behavior described in the setting and add separators as part of the #include auto complete feature.
Configuration and Logs
n/aOther Extensions
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
browntarik commentedon Dec 18, 2024
Not actionable due to bug that needs to be addressed by VS Code. Until it is addressed (microsoft/vscode#227012), we can't apply a reasonable fix.
bobbrow commentedon Dec 19, 2024
If we're not going to fix this, we should at least fix the setting's description.
[-]preferredPathSeparator does not seem to be respected in #include auto complete[/-][+]Description of preferredPathSeparator setting is incorrect[/+]