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
I have checked existing issues and there are no existing ones with the same request.
Feature description
Vale configuration - https://vale.sh/docs/topics/config/ - has a feature where the vale process scans up from the current directory to find the first .vale.ini configuration file in the current directory and any parent directory. It uses this configuration in addition to the global configuration. This allows per directory configuration to be set for vale processing.
The current implementation of the vale builtin for none-ls doesn't have a cwd function set and so falls back to setting cwd for the spawn process to the root directory for the nvim process. Vale in the current builtin implementation looks in that root folder and scans up through parent folders, however this misses the opportunity to do per-directory vale configuration.
Help
Yes - I have created a PR which I think implements this feature, thank you for any comments and thoughts on this.
Implementation help
If we set the cwd for the spawned vale process to the directory of the file being processed then we naturally pick up on the vale configuration from the directories and parent directory of the current file.
I suspect this is simply a matter of defining a cwd function for the vale builtin, e.g.
Issues
Feature description
Vale configuration - https://vale.sh/docs/topics/config/ - has a feature where the vale process scans up from the current directory to find the first
.vale.ini
configuration file in the current directory and any parent directory. It uses this configuration in addition to the global configuration. This allows per directory configuration to be set for vale processing.The current implementation of the vale builtin for none-ls doesn't have a cwd function set and so falls back to setting cwd for the spawn process to the root directory for the nvim process. Vale in the current builtin implementation looks in that root folder and scans up through parent folders, however this misses the opportunity to do per-directory vale configuration.
Help
Yes - I have created a PR which I think implements this feature, thank you for any comments and thoughts on this.
Implementation help
If we set the cwd for the spawned vale process to the directory of the file being processed then we naturally pick up on the vale configuration from the directories and parent directory of the current file.
I suspect this is simply a matter of defining a
cwd
function for the vale builtin, e.g.The text was updated successfully, but these errors were encountered: