Reference
This page lists every setting and command the extension contributes, grouped by purpose. Each name links to its full entry in the User Manual, with its default and examples.
Note
Every setting’s fully qualified name begins with ceedlingExplorer.. As an example, projects below is ceedlingExplorer.projects in settings.json. Command IDs begin with the same slug.
Projects
mixins— Ceedling mixins for every project without its ownprojects— The Ceedling projects in a workspace folderdebugLaunchConfig— Thelaunch.jsonconfiguration that debugs the projectmixins— The project’s own mixins, in place ofmixinsabovename— The project’s label in the Testing viewpath— The project’s directory or YAML file
Running Ceedling
ansiEscapeSequencesRemoved— Remove terminal colors from Ceedling’s outputceedlingCommand— The command that runs CeedlingshellPath— The shell Ceedling runs intestCommandArgs— Ceedling’s arguments for a test run
Test labels
prettyTestFileLabel— Shorten each test file’s labelprettyTestLabel— Shorten each test’s label
Code coverage
coverageCommandArgs— Ceedling’s arguments for a coverage runcoverageResetsCounters— Clear earlier runs’ coverage before each coverage run
Problem matching
problemMatching— Report compiler and linker problems in the editor
Pattern properties
Each custom pattern in problemMatching.patterns is an object with these properties. Only regexp, message, and file are required.
column— The capture group holding the first columnfile— The capture group holding the filefilePrefix— Prepended to a relative file pathlastColumn— The capture group holding the last columnlastLine— The capture group holding the last lineline— The capture group holding the first linemessage— The capture group holding the messageregexp— The regular expression matching a problem linescanStderr— Scan Ceedling’s stderrscanStdout— Scan Ceedling’s stdoutseverity— The severity of the problems found