Allow a clangd configuration to inherit values from another configuration #8

New issue

Closed

opened 2026-07-20 13:10:31 -04:00 by kevintl1998 · 0 comments

kevintl1998 commented

2026-07-20 13:10:31 -04:00

Owner

So a 'base' configuration can be created with common settings which can be reused. Will also help simplify configurations for larger projects.

Values in the inherited config should be overridden by values in the config inheriting it. e.g. inherited: {"defines": {"d1": "v1", "d2": "v2"}}, inheritee(?): {"defines": {"d1": "v3"}}, modified config: {"defines": {"d1": "v3", "d2": "v2"}}
Currently I think that this should be a flag option. e.g. "@<config>": "inherit=<other_config>"

So a 'base' configuration can be created with common settings which can be reused. Will also help simplify configurations for larger projects. Values in the inherited config should be overridden by values in the config inheriting it. e.g. inherited: `{"defines": {"d1": "v1", "d2": "v2"}}`, inheritee(?): `{"defines": {"d1": "v3"}}`, modified config: `{"defines": {"d1": "v3", "d2": "v2"}}` Currently I think that this should be a flag option. e.g. `"@<config>": "inherit=<other_config>"`

kevintl1998 added a new dependency

2026-07-20 13:17:07 -04:00

#9 allow selecting configuration from a list

kevintl1998 removed a dependency

2026-07-20 13:18:50 -04:00

#9 allow selecting configuration from a list

kevintl1998 added reference configuration_inheritance

2026-07-22 15:00:32 -04:00

kevintl1998 added the

Kind/Feature

label

2026-07-22 15:28:50 -04:00