@schemastore/clang-format 0.0.4

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Florian Imdahl. All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE

package/README.md

@@ -0,0 +1,12 @@
+# Installation
+> `npm install --save @schemastore/clang-format`
+
+# Summary
+This package contains type definitions for clang-format.
+
+## Details
+Files were exported from https://github.com/ffflorian/schemastore-updater/tree/main/schemas/clang-format.
+
+## Additional Details
+* Last updated: Tue, Jan 17, 2023, 20:16:45 GMT
+* Dependencies: none

package/index.d.ts

@@ -0,0 +1,1116 @@
+/* tslint:disable */
+/**
+ * This file was automatically generated by json-schema-to-typescript.
+ * DO NOT MODIFY IT BY HAND. Instead, modify the source JSONSchema file,
+ * and run json-schema-to-typescript to regenerate this file.
+ */
+
+/**
+ * The .clang-format file is a YAML file defining formatting styles used by clang-format.
+
+ see https://clang.llvm.org/docs/ClangFormatStyleOptions.html
+ */
+export interface ClangFormatConfig {
+  /**
+   * The style used for all options not specifically set in the configuration.
+   */
+  BasedOnStyle?:
+    | "Chromium"
+    | "Google"
+    | "LLVM"
+    | "Mozilla"
+    | "WebKit"
+    | "Microsoft"
+    | "GNU"
+    | "InheritParentConfig"
+    | "chromium"
+    | "google"
+    | "llvm"
+    | "mozilla"
+    | "webkit"
+    | "microsoft"
+    | "gnu"
+    | "inheritparentconfig";
+  /**
+ * clang-format 3.3
+
+ The extra indent or outdent of access modifiers, e.g. public:.
+ */
+  AccessModifierOffset?: number;
+  /**
+ * clang-format 3.8
+
+ This applies to round brackets (parentheses), angle brackets and square brackets.
+ */
+  AlignAfterOpenBracket?: "Align" | "DontAlign" | "AlwaysBreak" | "BlockIndent";
+  /**
+ *  clang-format 13
+
+ if not None, when using initialization for an array of structs aligns the fields into columns.
+ */
+  AlignArrayOfStructures?: "None" | "Left" | "Right";
+  /**
+ * clang-format 9
+
+ Style of aligning consecutive macros.
+ */
+  AlignConsecutiveMacros?:
+    | "None"
+    | "Consecutive"
+    | "AcrossEmptyLines"
+    | "AcrossComments"
+    | "AcrossEmptyLinesAndComments";
+  /**
+ * clang-format 3.8
+
+ Style of aligning consecutive assignments.
+ */
+  AlignConsecutiveAssignments?:
+    | "None"
+    | "Consecutive"
+    | "AcrossEmptyLines"
+    | "AcrossComments"
+    | "AcrossEmptyLinesAndComments";
+  /**
+ * clang-format 11
+
+ Style of aligning consecutive bit field.
+ */
+  AlignConsecutiveBitFields?:
+    | "None"
+    | "Consecutive"
+    | "AcrossEmptyLines"
+    | "AcrossComments"
+    | "AcrossEmptyLinesAndComments";
+  /**
+ * clang-format 3.8
+
+ Style of aligning consecutive declarations.
+ */
+  AlignConsecutiveDeclarations?:
+    | "None"
+    | "Consecutive"
+    | "AcrossEmptyLines"
+    | "AcrossComments"
+    | "AcrossEmptyLinesAndComments";
+  /**
+ * clang-format 5
+
+ Options for aligning backslashes in escaped newlines.
+ */
+  AlignEscapedNewlines?: "Left" | "Right" | "DontAlign";
+  /**
+ * clang-format 3.5
+
+ If true, horizontally align operands of binary and ternary expressions.
+ */
+  AlignOperands?: "Align" | "DontAlign" | "AlignAfterOperator";
+  /**
+ * clang-format 3.7
+
+ If true, aligns trailing comments.
+ */
+  AlignTrailingComments?: boolean;
+  /**
+ * clang-format 9
+
+ If a function call or braced initializer list doesn’t fit on a line, allow putting all arguments onto the next line, even if BinPackArguments is false.
+ */
+  AllowAllArgumentsOnNextLine?: boolean;
+  /**
+ * clang-format 9
+
+ This option is deprecated in clang-format 15. See NextLine of PackConstructorInitializers.
+
+ If a constructor definition with a member initializer list doesn’t fit on a single line, allow putting all member initializers onto the next line, if `ConstructorInitializerAllOnOneLineOrOnePerLine` is true. Note that this parameter has no effect if `ConstructorInitializerAllOnOneLineOrOnePerLine` is false.
+ */
+  AllowAllConstructorInitializersOnNextLine?: boolean;
+  /**
+ * clang-format 3.3
+
+ If the function declaration doesn’t fit on a line, allow putting all parameters of a function declaration onto the next line even if BinPackParameters is false.
+ */
+  AllowAllParametersOfDeclarationOnNextLine?: boolean;
+  /**
+ * clang-format 11
+
+ Allow short enums on a single line.
+ */
+  AllowShortEnumsOnASingleLine?: boolean;
+  /**
+ * clang-format 3.5
+
+ Dependent on the value, while (true) { continue; } can be put on a single line.
+ */
+  AllowShortBlocksOnASingleLine?: "Never" | "Empty" | "Always";
+  /**
+ * clang-format 3.6
+
+ If true, short case labels will be contracted to a single line.
+ */
+  AllowShortCaseLabelsOnASingleLine?: boolean;
+  /**
+ * clang-format 3.5
+
+ Dependent on the value, int f() { return 0; } can be put on a single line.
+ */
+  AllowShortFunctionsOnASingleLine?: "All" | "None" | "Inline" | "Empty" | "InlineOnly";
+  /**
+ * clang-format 9
+
+ Dependent on the value, auto lambda []() { return 0; } can be put on a single line.
+ */
+  AllowShortLambdasOnASingleLine?: "None" | "Empty" | "Inline" | "All";
+  /**
+ * clang-format 9
+
+ If true, if (a) return; can be put on a single line.
+ */
+  AllowShortIfStatementsOnASingleLine?: "AllIfsAndElse" | "Never" | "WithoutElse" | "OnlyFirstIf";
+  /**
+ * clang-format 3.7
+
+ If true, while (true) continue; can be put on a single line.
+ */
+  AllowShortLoopsOnASingleLine?: boolean;
+  /**
+ * clang-format 3.7
+
+ This option is deprecated and is retained for backwards compatibility.
+
+ The function definition return type breaking style to use. This option is deprecated and is retained for backwards compatibility
+ */
+  AlwaysBreakAfterDefinitionReturnType?: "None" | "All" | "TopLevel";
+  /**
+ * clang-format 3.8
+
+ The function declaration return type breaking style to use.
+ */
+  AlwaysBreakAfterReturnType?: "None" | "All" | "TopLevel" | "AllDefinitions" | "TopLevelDefinitions";
+  /**
+ * clang-format 3.4
+
+ If true, always break before multiline string literals.
+ */
+  AlwaysBreakBeforeMultilineStrings?: boolean;
+  /**
+ * clang-format 7
+
+ The template declaration breaking style to use.
+ */
+  AlwaysBreakTemplateDeclarations?: "Yes" | "No" | "MultiLine";
+  /**
+ * clang-format 12
+
+ A vector of strings that should be interpreted as attributes/qualifiers instead of identifiers. This can be useful for language extensions or static analyzer annotations.
+ */
+  AttributeMacros?: string[];
+  /**
+ * clang-format 3.7
+
+ If false, a function call’s arguments will either be all on the same line or will have one line each.
+ */
+  BinPackArguments?: boolean;
+  /**
+ * clang-format 3.7
+
+ If false, a function declaration’s or function definition’s parameters will either all be on the same line or will have one line each.
+ */
+  BinPackParameters?: boolean;
+  /**
+ * clang-format 12
+
+ The BitFieldColonSpacingStyle to use for bitfields.
+ */
+  BitFieldColonSpacing?: "Both" | "None" | "Before" | "After";
+  /**
+ * clang-format 3.8
+
+ Control of individual brace wrapping cases.If BreakBeforeBraces is set to BS_Custom, use this to specify how each individual brace case should be handled. Otherwise, this is ignored.
+ */
+  BraceWrapping?: {
+    /**
+     * bool AfterCaseLabel Wrap case labels.
+     */
+    AfterCaseLabel?: boolean;
+    /**
+     * bool AfterClass Wrap class definitions.
+     */
+    AfterClass?: boolean;
+    /**
+     * AfterControlStatement Wrap control statements (if/for/while/switch/..).
+     */
+    AfterControlStatement?: "Never" | "MultiLine" | "Always";
+    /**
+     * bool AfterEnum Wrap enum definitions.
+     */
+    AfterEnum?: boolean;
+    /**
+     * bool AfterFunction Wrap function definitions.
+     */
+    AfterFunction?: boolean;
+    /**
+     * bool AfterNamespace Wrap namespace definitions.
+     */
+    AfterNamespace?: boolean;
+    /**
+     * bool AfterObjCDeclaration Wrap ObjC definitions (interfaces, implementations…). @autoreleasepool and @synchronized blocks are wrapped according to AfterControlStatement flag.
+     */
+    AfterObjCDeclaration?: boolean;
+    /**
+     * bool AfterStruct Wrap struct definitions.
+     */
+    AfterStruct?: boolean;
+    /**
+     * bool AfterUnion Wrap union definitions.
+     */
+    AfterUnion?: boolean;
+    /**
+     * bool AfterExternBlock Wrap extern blocks.
+     */
+    AfterExternBlock?: boolean;
+    /**
+     * bool BeforeCatch Wrap before catch.
+     */
+    BeforeCatch?: boolean;
+    /**
+     * bool BeforeElse Wrap before else.
+     */
+    BeforeElse?: boolean;
+    /**
+     * bool BeforeLambdaBody Wrap lambda block.
+     */
+    BeforeLambdaBody?: boolean;
+    /**
+     * bool BeforeWhile Wrap before while.
+     */
+    BeforeWhile?: boolean;
+    /**
+     * bool IndentBraces Indent the wrapped braces themselves.
+     */
+    IndentBraces?: boolean;
+    /**
+     * bool SplitEmptyFunction If false, empty function body can be put on a single line. This option is used only if the opening brace of the function has already been wrapped, i.e. the AfterFunction brace wrapping mode is set, and the function could/should not be put on a single line (as per AllowShortFunctionsOnASingleLine and constructor formatting options).
+     */
+    SplitEmptyFunction?: boolean;
+    /**
+     * bool SplitEmptyRecord If false, empty record (e.g. class, struct or union) body can be put on a single line. This option is used only if the opening brace of the record has already been wrapped, i.e. the AfterClass (for classes) brace wrapping mode is set.
+     */
+    SplitEmptyRecord?: boolean;
+    /**
+     * bool SplitEmptyNamespace If false, empty namespace body can be put on a single line. This option is used only if the opening brace of the namespace has already been wrapped, i.e. the AfterNamespace brace wrapping mode is set.
+     */
+    SplitEmptyNamespace?: boolean;
+    [k: string]: unknown;
+  };
+  /**
+ * clang-format 3.8
+
+ Break after each annotation on a field in Java files.
+ */
+  BreakAfterJavaFieldAnnotations?: boolean;
+  /**
+ * clang-format 3.6
+
+ The way to wrap binary operators.
+ */
+  BreakBeforeBinaryOperators?: "None" | "NonAssignment" | "All";
+  /**
+ * clang-format 3.7
+
+ The brace breaking style to use.
+ */
+  BreakBeforeBraces?:
+    | "Attach"
+    | "Linux"
+    | "Mozilla"
+    | "Stroustrup"
+    | "Allman"
+    | "Whitesmiths"
+    | "GNU"
+    | "WebKit"
+    | "Custom";
+  BreakBeforeConceptDeclarations?: boolean | ("Never" | "Allowed" | "Always");
+  /**
+ * clnag-format 5
+
+ If true, in the class inheritance expression clang-format will break before : and , if there is multiple inheritance.
+ */
+  BreakBeforeInheritanceComma?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, ternary operators will be placed after line breaks.
+ */
+  BreakBeforeTernaryOperators?: boolean;
+  /**
+ * clang-format 5
+
+ The constructor initializers style to use.
+ */
+  BreakConstructorInitializers?: "BeforeColon" | "BeforeComma" | "AfterColon";
+  /**
+ * clang-format 7
+
+ The inheritance list style to use.
+ */
+  BreakInheritanceList?: "BeforeColon" | "BeforeComma" | "AfterColon" | "AfterComma";
+  /**
+ * clang-format 3.9
+
+ Allow breaking string literals when formatting.
+ */
+  BreakStringLiterals?: boolean;
+  /**
+ * clang-format 3.8
+
+ Always break constructor initializers before commas and align the commas with the colon.
+ */
+  BreakConstructorInitializersBeforeComma?: boolean;
+  /**
+ * clang-format 3.7
+
+ The column limit.
+ */
+  ColumnLimit?: number;
+  /**
+ * clang-format 3.7
+
+ A regular expression that describes comments with special meaning, which should not be split into lines or otherwise changed.
+ */
+  CommentPragmas?: string;
+  /**
+ * clang-format 5
+
+ If true, consecutive namespace declarations will be on the same line. If false, each namespace is declared on a new line.
+ */
+  CompactNamespaces?: boolean;
+  /**
+ * clang-format 3.7
+
+ This option is deprecated. See CurrentLine of PackConstructorInitializers.
+ */
+  ConstructorInitializerAllOnOneLineOrOnePerLine?: boolean;
+  /**
+ * clang-format 3.7
+
+ The number of characters to use for indentation of constructor initializer lists as well as inheritance lists.
+ */
+  ConstructorInitializerIndentWidth?: number;
+  /**
+ * clang-format 3.7
+
+ Indent width for line continuations.
+ */
+  ContinuationIndentWidth?: number;
+  /**
+ * clang-format 3.4
+
+ If true, format braced lists as best suited for C++11 braced lists.
+ */
+  Cpp11BracedListStyle?: boolean;
+  /**
+ * clang-format 10
+
+ Analyze the formatted file for the most used line ending (
+ *  or 
+ * ). UseCRLF is only used as a fallback if none can be derived.
+ */
+  DeriveLineEnding?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, analyze the formatted file for the most common alignment of & and *. Pointer and reference alignment styles are going to be updated according to the preferences found in the file. PointerAlignment is then used only as fallback.
+ */
+  DerivePointerAlignment?: boolean;
+  /**
+ * clang-format 3.7
+
+ Disables formatting completely.
+ */
+  DisableFormat?: boolean;
+  /**
+ * clang-format 13
+
+ Defines when to put an empty line after access modifiers. EmptyLineBeforeAccessModifier configuration handles the number of empty lines between two access modifiers.
+ */
+  EmptyLineAfterAccessModifier?: "Never" | "Leave" | "Always";
+  /**
+ * clang-format 12
+
+ Defines in which cases to put empty line before access modifiers.
+ */
+  EmptyLineBeforeAccessModifier?: "LogicalBlock" | "Never" | "Leave" | "Always";
+  /**
+ * clang-format 3.7
+
+ If true, clang-format detects whether function calls and definitions are formatted with one parameter per line.
+ */
+  ExperimentalAutoDetectBinPacking?: boolean;
+  /**
+ * clang-format 5
+
+ If true, clang-format adds missing namespace end comments for short namespaces and fixes invalid existing ones. Short ones are controlled by “ShortNamespaceLines”.
+ */
+  FixNamespaceComments?: boolean;
+  /**
+ * clang-format 3.7
+
+ A vector of macros that should be interpreted as foreach loops instead of as function calls.
+ */
+  ForEachMacros?: string[];
+  /**
+ * clang-format 13
+
+ A vector of macros that should be interpreted as conditionals instead of as function calls.
+ */
+  IfMacros?: string[];
+  /**
+ * clang-format 7
+
+ Dependent on the value, multiple #include blocks can be sorted as one and divided based on category.
+ */
+  IncludeBlocks?: "Regroup" | "Preserve" | "Merge";
+  /**
+ * clang-format 7
+
+ Regular expressions denoting the different #include categories used for ordering #includes. If none of the regular expressions match, INT_MAX is assigned as category.The main header for a source file automatically gets category 0. so that it is generally kept at the beginning of the #includes (https://llvm.org/docs/CodingStandards.html#include-style). However, you can also assign negative priorities if you have certain headers that always need to be first. 
+ There is a third and optional field SortPriority which can used while IncludeBlocks = IBS_Regroup to define the priority in which #includes should be ordered. The value of Priority defines the order of #include blocks and also allows the grouping of #includes of different priority. SortPriority is set to the value of Priority as default if it is not assigned.
+ */
+  IncludeCategories?: {
+    Regex: string;
+    Priority: number;
+    SortPriority?: number;
+    CaseSensitive?: boolean;
+    [k: string]: unknown;
+  }[];
+  /**
+ * clang-format 7
+
+ Specify a regular expression of suffixes that are allowed in the file-to-main-include mapping.
+When guessing whether a #include is the “main” include (to assign category 0, see above), use this regex of allowed suffixes to the header stem. A partial match is done, so that: - “” means “arbitrary suffix” - “$” means “no suffix”
+For example, if configured to “(_test)?$”, then a header a.h would be seen as the “main” include in both a.cc and a_test.cc.
+ */
+  IncludeIsMainRegex?: string;
+  /**
+ * clang-format 7
+
+ Specify a regular expression for files being formatted that are allowed to be considered “main” in the file-to-main-include mapping.
+By default, clang-format considers files as “main” only when they end with: .c, .cc, .cpp, .c++, .cxx, .m or .mm extensions. For these files a guessing of “main” include takes place (to assign category 0, see above). This config option allows for additional suffixes and extensions for files to be considered as “main”.
+By default, clang-format considers files as “main” only when they end with: .c, .cc, .cpp, .c++, .cxx, .m or .mm extensions. For these files a guessing of “main” include takes place (to assign category 0, see above). This config option allows for additional suffixes and extensions for files to be considered as “main”. 
+ */
+  IncludeIsMainSourceRegex?: string;
+  /**
+ * clang-format 13
+
+ Specify whether access modifiers should have their own indentation level.
+When false, access modifiers are indented (or outdented) relative to the record members, respecting the AccessModifierOffset. Record members are indented one level below the record. When true, access modifiers get their own indentation level. As a consequence, record members are always indented 2 levels below the record, regardless of the access modifier presence. Value of the AccessModifierOffset is ignored.
+ */
+  IndentAccessModifiers?: boolean;
+  /**
+ * clang-format 11
+
+ Indent case label blocks one level from the case label.
+When false, the block following the case label uses the same indentation level as for the case label, treating the case label the same as an if-statement. When true, the block gets indented as a scope block.
+ */
+  IndentCaseBlocks?: boolean;
+  /**
+ * clang-format 3.3
+
+ Indent case labels one level from the switch statement.
+When false, use the same indentation level as for the switch statement. Switch statement body is always indented one level more than case labels (except the first block following the case label, which itself indents the code - unless IndentCaseBlocks is enabled).
+ */
+  IndentCaseLabels?: boolean;
+  /**
+ * clang-format 11
+
+ IndentExternBlockStyle is the type of indenting of extern blocks.
+ */
+  IndentExternBlock?: "AfterExternBlock" | "NonIndent" | "Indent";
+  /**
+ * clang-format 10
+
+ Indent goto labels.
+When false, goto labels are flushed left.
+ */
+  IndentGotoLabels?: boolean;
+  /**
+ * clang-format 6
+
+ The preprocessor directive indenting style to use.
+ */
+  IndentPPDirectives?: "None" | "AfterHash" | "BeforeHash";
+  /**
+ * clang-format 15
+
+ Indent the requires clause in a template. This only applies when RequiresClausePosition is OwnLine, or WithFollowing.
+ */
+  IndentRequiresClause?: boolean;
+  /**
+ * clang-format 12-14
+
+ Indent the requires clause in a template. This only applies when RequiresClausePosition is OwnLine, or WithFollowing. In clang-format 12, 13 and 14 it was named IndentRequires.
+ */
+  IndentRequires?: boolean;
+  /**
+ * clang-format 3.7
+
+ The number of columns to use for indentation.
+ */
+  IndentWidth?: number;
+  /**
+ * clang-format 3.7
+
+ Indent if a function definition or declaration is wrapped after the type.
+ */
+  IndentWrappedFunctionNames?: boolean;
+  /**
+ * clang-fomrat 15
+ Insert braces after control statements (if, else, for, do, and while) in C++ unless the control statements are inside macro definitions or the braces would enclose preprocessor directives.
+
+ Warning: Setting this option to true could lead to incorrect code formatting due to clang-format’s lack of complete semantic information. As such, extra care should be taken to review code changes made by this option.
+ */
+  InsertBraces?: boolean;
+  /**
+ * clang-fromat 11
+
+ If set to TCS_Wrapped will insert trailing commas in container literals (arrays and objects) that wrap across multiple lines. It is currently only available for JavaScript and disabled by default TCS_None. InsertTrailingCommas cannot be used together with BinPackArguments as inserting the comma disables bin-packing.
+ */
+  InsertTrailingCommas?: "None" | "Wrapped";
+  /**
+ * clang-format 8
+
+ The JavaScriptQuoteStyle to use for JavaScript strings.
+ */
+  JavaImportGroup?: unknown[];
+  /**
+ * clang-fromat 3.9
+
+ The JavaScriptQuoteStyle to use for JavaScript strings.
+ */
+  JavaScriptQuotes?: "Leave" | "Single" | "Double";
+  /**
+ * clang-format 3.9
+
+ Whether to wrap JavaScript import/export statements.
+ */
+  JavaScriptWrapImports?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, the empty line at the start of blocks is kept.
+ */
+  KeepEmptyLinesAtTheStartOfBlocks?: boolean;
+  /**
+ * clang-format 13
+
+ The indentation style of lambda bodies. Signature (the default) causes the lambda body to be indented one additional level relative to the indentation level of the signature. OuterScope forces the lambda body to be indented one additional level relative to the parent scope containing the lambda signature. For callback-heavy code, it may improve readability to have the signature indented two levels and to use OuterScope. The KJ style guide requires OuterScope. KJ style guide
+ */
+  LambdaBodyIndentation?: "Signature" | "OuterScope";
+  /**
+ * clang-format 3.5
+
+ Language, this format style is targeted at.
+ */
+  Language?: "None" | "Cpp" | "ObjC" | "CSharp" | "Java" | "JavaScript" | "Json" | "Proto" | "TableGen" | "TextProto";
+  /**
+ * clang-format 3.7
+
+ A regular expression matching macros that start a block.
+ */
+  MacroBlockBegin?: string;
+  /**
+ * clang-format 3.7
+
+ A regular expression matching macros that end a block.
+ */
+  MacroBlockEnd?: string;
+  /**
+ * clang-format 3.7
+
+ The maximum number of consecutive empty lines to keep.
+ */
+  MaxEmptyLinesToKeep?: number;
+  /**
+ * clnag-format 3.7
+
+ The indentation used for namespaces.
+ */
+  NamespaceIndentation?: "None" | "Inner" | "All";
+  /**
+ * clnag-format 9
+
+ A vector of macros which are used to open namespace blocks.
+ */
+  NamespaceMacros?: string[];
+  /**
+ * clang-format 7
+
+ Controls bin-packing Objective-C protocol conformance list items into as few lines as possible when they go over ColumnLimit.If Auto (the default), delegates to the value in BinPackParameters. If that is true, bin-packs Objective-C protocol conformance list items into as few lines as possible whenever they go over ColumnLimit.
+If Always, always bin-packs Objective-C protocol conformance list items into as few lines as possible whenever they go over ColumnLimit.
+If Never, lays out Objective-C protocol conformance list items onto individual lines whenever they go over ColumnLimit.
+ */
+  ObjCBinPackProtocolList?: "Never" | "Auto" | "Always";
+  /**
+ * clang-format 3.7
+
+ The number of characters to use for indentation of ObjC blocks.
+ */
+  ObjCBlockIndentWidth?: number;
+  /**
+ * clang-format 11
+
+ Break parameters list into lines when there is nested block parameters in a function call.
+ */
+  ObjCBreakBeforeNestedBlockParam?: boolean;
+  /**
+ * clang-format 3.7
+
+ Add a space after @property in Objective-C, i.e. use @property (readonly) instead of @property(readonly).
+ */
+  ObjCSpaceAfterProperty?: boolean;
+  /**
+ * clang-format 3.7
+
+ Add a space in front of an Objective-C protocol list, i.e. use Foo <Protocol> instead of Foo<Protocol>.
+ */
+  ObjCSpaceBeforeProtocolList?: boolean;
+  /**
+ * clang-format 13
+
+ The number of columns to use for indentation of preprocessor statements. When set to -1 (default) IndentWidth is used also for preprocessor statements.
+ */
+  PPIndentWidth?: number;
+  /**
+ * clang-format 14
+
+ The pack constructor initializers style to use.
+ */
+  PackConstructorInitializers?: "Never" | "BinPack" | "CurrentLine" | "NextLine";
+  /**
+ * clang-format 5
+
+ The penalty for breaking around an assignment operator.
+ */
+  PenaltyBreakAssignment?: number;
+  /**
+ * clang-format 3.7
+
+ The penalty for breaking a function call after call(.
+ */
+  PenaltyBreakBeforeFirstCallParameter?: number;
+  /**
+ * clang-format 3.7
+
+ The penalty for each line break introduced inside a comment.
+ */
+  PenaltyBreakComment?: number;
+  /**
+ * clang-format 3.7
+
+ The penalty for breaking before the first <<.
+ */
+  PenaltyBreakFirstLessLess?: number;
+  /**
+ * clang-format 14
+
+ The penalty for breaking after (.
+ */
+  PenaltyBreakOpenParenthesis?: number;
+  /**
+ * clang-format 3.7
+
+ The penalty for each line break introduced inside a string literal.
+ */
+  PenaltyBreakString?: number;
+  /**
+ * clang-format 7
+
+ The penalty for breaking after template declaration.
+ */
+  PenaltyBreakTemplateDeclaration?: number;
+  /**
+ * clang-format 3.7
+
+ The penalty for each character outside of the column limit.
+ */
+  PenaltyExcessCharacter?: number;
+  /**
+ * clang-format 12
+
+ Penalty for each character of whitespace indentation (counted relative to leading non-whitespace column).
+ */
+  PenaltyIndentedWhitespace?: number;
+  /**
+ * clang-format 3.7
+
+ Penalty for putting the return type of a function onto its own line.
+ */
+  PenaltyReturnTypeOnItsOwnLine?: number;
+  /**
+ * clang-format 3.7
+
+ Pointer and reference alignment style.
+ */
+  PointerAlignment?: "Left" | "Right" | "Middle";
+  /**
+ * clang-format 14
+
+ Different ways to arrange specifiers and qualifiers (e.g. const/volatile).
+
+ Warning:Setting QualifierAlignment to something other than Leave, COULD lead to incorrect code formatting due to incorrect decisions made due to clang-formats lack of complete semantic information.
+
+ As such extra care should be taken to review code changes made by the use of this option.
+ */
+  QualifierAlignment?: "Leave" | "Left" | "Right" | "Custom";
+  /**
+ * clang-format 14
+
+ The order in which the qualifiers appear. Order is an array that can contain any of the following. 
+
+ Note: it MUST contain ‘type’. Items to the left of ‘type’ will be placed to the left of the type and aligned in the order supplied. Items to the right of ‘type’ will be placed to the right of the type and aligned in the order supplied.
+ */
+  QualifierOrder?: ("const" | "inline" | "static" | "constexpr" | "volatile" | "restrict" | "type")[];
+  /**
+ * clang-format 6
+
+ Defines hints for detecting supported languages code blocks in raw strings.
+ */
+  RawStringFormats?: {
+    /**
+ * clang-format 3.5
+
+ Language, this format style is targeted at.
+ */
+    Language?: "None" | "Cpp" | "ObjC" | "CSharp" | "Java" | "JavaScript" | "Json" | "Proto" | "TableGen" | "TextProto";
+    Delimiters?: string[];
+    CanonicalDelimiter?: string;
+    /**
+     * The style used for all options not specifically set in the configuration.
+     */
+    BasedOnStyle?:
+      | "Chromium"
+      | "Google"
+      | "LLVM"
+      | "Mozilla"
+      | "WebKit"
+      | "Microsoft"
+      | "GNU"
+      | "InheritParentConfig"
+      | "chromium"
+      | "google"
+      | "llvm"
+      | "mozilla"
+      | "webkit"
+      | "microsoft"
+      | "gnu"
+      | "inheritparentconfig";
+    EnclosingFunctions?: string[];
+    [k: string]: unknown;
+  }[];
+  /**
+ * clang-format 13
+
+ Reference alignment style (overrides PointerAlignment for references).
+ */
+  ReferenceAlignment?: "Pointer" | "Left" | "Right" | "Middle";
+  /**
+ * clang-format 4
+
+ If true, clang-format will attempt to re-flow comments.
+ */
+  ReflowComments?: boolean;
+  /**
+ * clang-format 14
+
+ Remove optional braces of control statements (if, else, for, and while) in C++ according to the LLVM coding style. 
+
+ WarningThis option will be renamed and expanded to support other styles.
+
+ Setting this option to true could lead to incorrect code formatting due to clang-format’s lack of complete semantic information. As such, extra care should be taken to review code changes made by this option.
+ */
+  RemoveBracesLLVM?: boolean;
+  /**
+ * clang-format 15
+
+ The position of the requires clause.
+ */
+  RequiresClausePosition?: "OwnLine" | "WithPreceding" | "WithFollowing" | "SingleLine";
+  /**
+ * clang-format 14
+
+ Specifies the use of empty lines to separate definition blocks, including classes, structs, enums, and functions.
+ */
+  SeparateDefinitionBlocks?: "Leave" | "Always" | "Never";
+  /**
+ * clang-format 13
+
+ The maximal number of unwrapped lines that a short namespace spans. Defaults to 1.
+ */
+  ShortNamespaceLines?: number;
+  /**
+ * clang-format 4
+
+ Controls if and how clang-format will sort #includes. If Never, includes are never sorted. If CaseInsensitive, includes are sorted in an ASCIIbetical or case insensitive fashion. If CaseSensitive, includes are sorted in an alphabetical or case sensitive fashion.
+ */
+  SortIncludes?: "CaseSensitive" | "CaseInsensitive" | "Never";
+  /**
+ * clang-format 12
+
+ When sorting Java imports, by default static imports are placed before non-static imports. If JavaStaticImportAfterImport is After, static imports are placed after non-static imports.
+ */
+  SortJavaStaticImport?: "Before" | "After";
+  /**
+ * clang-format 5
+
+ If true, clang-format will sort using declarations.
+ */
+  SortUsingDeclarations?: boolean;
+  /**
+ * clang-format 3.5
+
+ If true, a space is inserted after C style casts.
+ */
+  SpaceAfterCStyleCast?: boolean;
+  /**
+ * clang-format 9
+
+ If true, a space is inserted after the logical not operator (!).
+ */
+  SpaceAfterLogicalNot?: boolean;
+  /**
+ * clang-format 4
+
+ If true, a space will be inserted after the ‘template’ keyword.
+ */
+  SpaceAfterTemplateKeyword?: boolean;
+  /**
+ * clang-format 12
+
+ Defines in which cases to put a space before or after pointer qualifiers
+ */
+  SpaceAroundPointerQualifiers?: "Default" | "Before" | "After" | "Both";
+  /**
+ * clang-format 3.7
+
+ If false, spaces will be removed before assignment operators.
+ */
+  SpaceBeforeAssignmentOperators?: boolean;
+  /**
+ * clang-format 12
+
+ If false, spaces will be removed before case colon.
+ */
+  SpaceBeforeCaseColon?: boolean;
+  /**
+ * clang-format 7
+
+ If true, a space will be inserted before a C++11 braced list used to initialize an object (after the preceding identifier or type).
+ */
+  SpaceBeforeCpp11BracedList?: boolean;
+  /**
+ * clang-format 7
+
+ If false, spaces will be removed before constructor initializer colon.
+ */
+  SpaceBeforeCtorInitializerColon?: boolean;
+  /**
+ * clang-format 7
+
+ If false, spaces will be removed before inheritance colon.
+ */
+  SpaceBeforeInheritanceColon?: boolean;
+  /**
+ * clang-format 3.5
+
+ Defines in which cases to put a space before opening parentheses.
+ */
+  SpaceBeforeParens?:
+    | "ControlStatements"
+    | "Never"
+    | "ControlStatementsExceptControlMacros"
+    | "NonEmptyParentheses"
+    | "Always"
+    | "Custom";
+  /**
+ * clang-format 14
+
+ Control of individual space before parentheses.
+
+ If SpaceBeforeParens is set to Custom, use this to specify how each individual space before parentheses case should be handled. Otherwise, this is ignored.
+ */
+  SpaceBeforeParensOptions?: {
+    /**
+     * bool AfterControlStatements If true, put space betwee control statement keywords (for/if/while…) and opening parentheses.
+     */
+    AfterControlStatements?: boolean;
+    /**
+     * bool AfterForeachMacros If true, put space between foreach macros and opening parentheses.
+     */
+    AfterForeachMacros?: boolean;
+    /**
+     * bool AfterFunctionDeclarationName If true, put a space between function declaration name and opening parentheses.
+     */
+    AfterFunctionDeclarationName?: boolean;
+    /**
+     * bool AfterFunctionDefinitionName If true, put a space between function definition name and opening parentheses.
+     */
+    AfterFunctionDefinitionName?: boolean;
+    /**
+     * bool AfterIfMacros If true, put space between if macros and opening parentheses.
+     */
+    AfterIfMacros?: boolean;
+    /**
+     * bool AfterOverloadedOperator If true, put a space between operator overloading and opening parentheses.
+     */
+    AfterOverloadedOperator?: boolean;
+    /**
+     * bool AfterRequiresInClause If true, put space between requires keyword in a requires clause and opening parentheses, if there is one.
+     */
+    AfterRequiresInClause?: boolean;
+    /**
+     * bool AfterRequiresInExpression If true, put space between requires keyword in a requires expression and opening parentheses.
+     */
+    AfterRequiresInExpression?: boolean;
+    /**
+     * bool BeforeNonEmptyParentheses If true, put a space before opening parentheses only if the parentheses are not empty.
+     */
+    BeforeNonEmptyParentheses?: boolean;
+    [k: string]: unknown;
+  };
+  /**
+ * clang-format 7
+
+ If false, spaces will be removed before range-based for loop colon.
+ */
+  SpaceBeforeRangeBasedForLoopColon?: boolean;
+  /**
+ * clang-format 10
+
+ If true, spaces will be before [. Lambdas will not be affected. Only the first [ will get a space added.
+ */
+  SpaceBeforeSquareBrackets?: boolean;
+  /**
+ * clang-format 10
+
+ If true, spaces will be inserted into {}.
+ */
+  SpaceInEmptyBlock?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, spaces may be inserted into ().
+ */
+  SpaceInEmptyParentheses?: boolean;
+  /**
+ * clang-format 3.7
+
+ The number of spaces before trailing line comments (// - comments).
+
+This does not affect trailing block comments (/* - comments) as those commonly have different usage patterns and a number of special cases.
+ */
+  SpacesBeforeTrailingComments?: number;
+  /**
+ * clang-format 3.4
+
+ The SpacesInAnglesStyle to use for template argument lists.
+ */
+  SpacesInAngles?: "Never" | "Always" | "Leave";
+  /**
+ * clang-format 3.7
+
+ If true, spaces may be inserted into C style casts.
+ */
+  SpacesInCStyleCastParentheses?: boolean;
+  /**
+ * clang-format 10
+
+ If true, spaces will be inserted around if/for/switch/while conditions.
+ */
+  SpacesInConditionalStatement?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, spaces are inserted inside container literals (e.g. ObjC and Javascript array and dict literals).
+ */
+  SpacesInContainerLiterals?: boolean;
+  /**
+ * clang-format 13
+
+ How many spaces are allowed at the start of a line comment. To disable the maximum set it to -1, apart from that the maximum takes precedence over the minimum.
+ */
+  SpacesInLineCommentPrefix?: {
+    Minimum?: number;
+    Maximum?: number;
+    [k: string]: unknown;
+  };
+  /**
+ * clang-format 3.7
+
+ If true, spaces will be inserted after ( and before ).
+ */
+  SpacesInParentheses?: boolean;
+  /**
+ * clang-format 3.7
+
+ If true, spaces will be inserted after [ and before ]. Lambdas without arguments or unspecified size array declarations will not be affected.
+ */
+  SpacesInSquareBrackets?: boolean;
+  /**
+ * clang-format 3.7
+
+ Parse and format C++ constructs compatible with this standard.
+ */
+  Standard?: "Auto" | "Latest" | "c++03" | "c++11" | "c++14" | "c++17" | "c++20";
+  /**
+ * clang-format 12
+
+ Macros which are ignored in front of a statement, as if they were an attribute. So that they are not parsed as identifier, for example for Qts emit.
+ */
+  StatementAttributeLikeMacros?: string[];
+  /**
+ * clnag-format 8
+
+ A vector of macros that should be interpreted as complete statements.
+
+ Typical macros are expressions, and require a semi-colon to be added; sometimes this is not the case, and this allows to make clang-format aware of such cases.
+ */
+  StatementMacros?: string[];
+  /**
+ * clang-format 3.7
+
+ The number of columns used for tab stops.
+ */
+  TabWidth?: number;
+  /**
+ * clang-format 9
+
+ A vector of macros that should be interpreted as type declarations instead of as function calls.
+
+For example: OpenSSL STACK_OF, BSD LIST_ENTRY.
+ */
+  TypenameMacros?: string[];
+  /**
+ * clang-format 10
+
+ Use 
+ *  instead of 
+ *  for line breaks. Also used as fallback if DeriveLineEnding is true.
+ */
+  UseCRLF?: boolean;
+  /**
+ * clang-format 3.7
+
+ The way to use tab characters in the resulting file.
+ */
+  UseTab?: "Never" | "ForIndentation" | "ForContinuationAndIndentation" | "AlignWithSpaces" | "Always";
+  /**
+ * clang-format 11
+
+ A vector of macros which are whitespace-sensitive and should not be touched.
+
+ For example: BOOST_PP_STRINGIZE
+ */
+  WhitespaceSensitiveMacros?: string[];
+  [k: string]: unknown;
+}

package/package.json

@@ -0,0 +1,14 @@
+{
+  "author": "Florian Imdahl <git@ffflorian.de>",
+  "dependencies": {},
+  "description": "TypeScript definitions for clang-format.",
+  "license": "MIT",
+  "main": "index.d.ts",
+  "name": "@schemastore/clang-format",
+  "repository": "https://github.com/ffflorian/schemastore-updater/tree/main/schemas/clang-format",
+  "scripts": {},
+  "typesPublisherContentHash": "7059cb1a5236593057c1d15912ae187e8030f5d9ffe137282bbd5ae7f2327ee4",
+  "types": "index.d.ts",
+  "version": "0.0.4",
+  "typeScriptVersion": "2.2"
+}