Improve workflow to edit/create clangd configurations #15

New issue

Open

opened 2026-07-21 14:40:13 -04:00 by kevintl1998 · 0 comments

kevintl1998 commented

2026-07-21 14:40:13 -04:00

Owner

Possible features:

User command to edit the contents of a single configuration
User command to create a new configuration

To implement this, we need to determine which Yapp configuration to save the config to. e.g. If a Yapp project and global configuration are merged together to form a single clangd configuration, which one should the edit be stored in? - project configuration makes the most sense because you shouldn't be able to implicitly update global or any other configuration external to the current project.

In the case where a value was edited which was sourced from not the project configuration, a new entry for it should be added in the project configuration since Yapp's expected behavior is to have the project configuration take precedence over all others.

Possible features: - User command to edit the contents of a single configuration - User command to create a new configuration To implement this, we need to determine which Yapp configuration to save the config to. e.g. If a Yapp project and global configuration are merged together to form a single clangd configuration, which one should the edit be stored in? - project configuration makes the most sense because you shouldn't be able to implicitly update global or any other configuration external to the current project. In the case where a value was edited which was sourced from not the project configuration, a new entry for it should be added in the project configuration since Yapp's expected behavior is to have the project configuration take precedence over all others.

kevintl1998 referenced this issue from kevintl1998/yapp.nvim

2026-07-21 16:14:58 -04:00

Improved workflow for editing configurations #23

kevintl1998 added the

Kind/Feature

label

2026-07-22 15:27:45 -04:00