Gaspar
3.0Schema URL
Properties
Options for outputting Models and Enums
5 nested properties
Output options. You must supply at least one of these.
List of file locations containing the models or controllers you wish to translate. Optional, if not provided will use all .cs files in the project.
[
"./**/*.cs"
]
List of file locations to exclude from the Include list
Enums will be written with their value, either set directly or from an Attribute (e.g. [EnumMember(Value = "name")]).
For TypeScript, if true will export enums as types instead of TypeScript enums.
Options for outputting service communication contracts for Controllers
6 nested properties
Output options. You must supply at least one of these.
Used to name exported items, can also be used in paths.
List of file locations containing the models or controllers you wish to translate. Optional, if not provided will use all .cs files in the project.
[
"./**/*.cs"
]
List of file locations to exclude from the Include list
Used by Ocelot Export, and can be used in paths. Typically set to 'http' or 'https'
Used by Ocelot Export, and can be used in paths.
Export names to run multiple outputs under a single name. e.g. Specify a group type called 'App' and add 'Swift' and 'Kotlin'
For TypeScript, Angular, Swift, Kotlin and Proto, you can override type names to objects each language will understand.
For TypeScript, Angular, Swift, Kotlin and Proto, you can override type names to objects the exported language will understand. These will apply equally to all exports, 'TypeTranslations' may be more useful
If the file output location cannot be found, you will get a build error; add "IgnoreMissingOutputLocations": true to skip the error. This is useful when you need to build in an environment where the output may not be available (e.g. docker); although it would usually be preferable to use dotnet build /p:RunGaspar=False in your scripts.
Set this to true to export all objects irrespective if they have [ExportFor] or not.