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
## Details
Adds support for an `overrides` field that allows for essentially a full
configuration per buftype. If no configuration is specified for a
particular buftype or a partial configuration the logic falls back to
the top level configuration. The top level configuration can be viewed
as the default and then overrides change it for specific buffers.
Because this mechanism is much more powerful it deprecates all other
buftype options as they can now be accomplished via this new mechanism.
The equivalents are as follows:
- `exclude.buftypes.<value>` -> `overrides.buftype.<value>.enabled = false`
- `sign.exclude.buftypes.<value>` -> `overrides.buftype.<value>.sign.enabled = false`
The previous default behavior of not showing signs on LSP floating
docs has been ported over, so anyone using default configurations
should not experience any problems.
Since the configuration is accessed all through the codebase there is a
pretty large code change here, but a lot if it is passing the new
resolved configuration around.
This enables a feature like different code padding by default vs. in LSP
floating windows with:
```lua
require('render-markdown').setup({
code = { left_pad = 4 },
overrides = {
buftype = {
nofile = {
code = { left_pad = 0 },
},
},
},
})
```
- Remove `profile` field in favor of benches [2f21726](https://github.com/MeanderingProgrammer/markdown.nvim/commit/2f217266c6b416c4948ddb7e88a5db02670c75d5)
12
+
- Remove `profile` field in favor of benches [dcfa033](https://github.com/MeanderingProgrammer/markdown.nvim/commit/dcfa033cb39bc4f30019925aa91d3af5ec049614)
13
13
- In order to fix:
14
14
- Implement `parse` method instead of `render`, no direct translation
15
15
-`profile` field was only meant for development, should not have any users
0 commit comments