projektor.json

description:
Global settings
https://github.com/yamnikov-oleg/projektor#configuration

title: keybinding

description:
A daemon keybinding
https://github.com/yamnikov-oleg/projektor#configuration

type: string

title: force cache interval

description:
A delay between daemon run with '-dry' flag
https://github.com/yamnikov-oleg/projektor#configuration

type: integer

title: enabled categories

description:
Global enabled category settings
https://github.com/yamnikov-oleg/projektor#configuration

type: object

title: calculator

description:
Whether to enable calculator
https://github.com/yamnikov-oleg/projektor#configuration

title: history

description:
Whether to show history
https://github.com/yamnikov-oleg/projektor#configuration

title: applications

description:
Whether to show applications
https://github.com/yamnikov-oleg/projektor#configuration

title: url

description:
Whether to show urls
https://github.com/yamnikov-oleg/projektor#configuration

title: commands

description:
Whether to show commands
https://github.com/yamnikov-oleg/projektor#configuration

title: files

description:
Whether to show files
https://github.com/yamnikov-oleg/projektor#configuration

title: web search

description:
Whether to allow web search
https://github.com/yamnikov-oleg/projektor#configuration

title: history

description:
Global history settings
https://github.com/yamnikov-oleg/projektor#configuration

title: capacity

description:
A capacity
https://github.com/yamnikov-oleg/projektor#configuration

title: url

description:
Global url settings
https://github.com/yamnikov-oleg/projektor#configuration

title: icon

description:
An icon
https://github.com/yamnikov-oleg/projektor#configuration

default: web-browser

title: websearch

description:
Global web search settings
https://github.com/yamnikov-oleg/projektor#configuration

title: engine

description:
A url template
https://github.com/yamnikov-oleg/projektor#configuration

title: icon

description:
An entry icon
https://github.com/yamnikov-oleg/projektor#configuration

title: ui

description:
Global UI settings
https://github.com/yamnikov-oleg/projektor#configuration

title: width

description:
A width
https://github.com/yamnikov-oleg/projektor#configuration

title: height

description:
A height
https://github.com/yamnikov-oleg/projektor#configuration

title: settings


npmpackagejsonlintrc.json

description:
npm-package-json-lint rule

"off" - turns the rule off
"warning" - turns the rule on as a warning, which doesn't affect the exit code
"error" - turns the rule on as an error, which when triggered generates an exit code of 2

enum: off warning error

type: array

$ref: #/definitions/rule

description: Require author property.

description: Require bin property.

description: Require bugs property.

description: Require bundledDependencies property.

description: Require config property.

description: Require contributors property.

description: Require cpu property.

description: Require dependencies property.

description: Require description property.

description: Require devDependencies property.

description: Require directories property.

description: Require engines property.

description: Require files property.

description: Require homepage property.

description: Require keywords property.

description: Require license property.

description: Require main property.

description: Require man property.

description: Require module property.

description: Require name property.

description: Require optionalDependencies property.

description: Require os property.

description: Require peerDependencies property.

description: Require preferGlobal property.

description: Require private property.

description: Require publishConfig property.

description: Require repository property.

description: Require scripts property.

description: Require version property.

description: Ensure the proper data type is used for bin.

description: Ensure the proper data type is used for bundledDependencies.

description: Ensure the proper data type is used for config.

description: Ensure the proper data type is used for cpu.

description: Ensure the proper data type is used for dependencies.

description: Ensure the proper data type is used for description.

description: Ensure the proper data type is used for devDependencies.

description: Ensure the proper data type is used for directories.

description: Ensure the proper data type is used for engines.

description: Ensure the proper data type is used for files.

description: Ensure the proper data type is used for homepage.

description: Ensure the proper data type is used for keywords.

description: Ensure the proper data type is used for license.

description: Ensure the proper data type is used for main.

description: Ensure the proper data type is used for man.

description: Ensure the proper data type is used for name.

description: Ensure the proper data type is used for optionalDependencies.

description: Ensure the proper data type is used for os.

description: Ensure the proper data type is used for peerDependencies.

description: Ensure the proper data type is used for preferGlobal.

description: Ensure the proper data type is used for private.

description: Ensure the proper data type is used for repository.

description: Ensure the proper data type is used for scripts.

description: Ensure the proper data type is used for version.

description: Requires author to equal one of the supplied values.

description: Requires engines to equal one of the supplied values.

description: Requires license to equal one of the supplied values.

description: Requires the scope used for the name to equal one of the supplied values.

description: Requires private to equal one of the supplied values.

description: Requires publishConfig to equal one of the supplied values.

description: Restrict dependencies from specifying an absolute version.

description: Restrict dependencies from using caret version syntax.

description: Restrict a list of dependencies.

description: Restrict listed dependencies from using pre-release versions.

description: Restrict dependencies from using tilde version syntax.

description: Restrict dependencies from specifying version 0.x.x modules.

description: Require all dependencies to use absolute versions.

description: Require all dependencies to use caret version syntax.

description: Require all dependencies to use tilde version syntax.

description: Require dependencies to be listed in alphabetical order.

description: Restrict devDependencies from specifying an absolute version.

description: Restrict devDependencies from using caret version syntax.

description: Restrict a list of devDependencies.

description: Restrict listed devDependencies from using pre-release versions.

description: Restrict devDependencies from using tilde version syntax.

description: Restrict devDependencies from specifying version 0.x.x modules.

description: Require all devDependencies to use absolute versions.

description: Require all devDependencies to use caret version syntax.

description: Require all devDependencies to use tilde version syntax.

description: Require devDependencies to be listed in alphabetical order.

description: Require bundledDependencies to be listed in alphabetical order.

description: Require optionalDependencies to be listed in alphabetical order.

description: Require peerDependencies to be listed in alphabetical order.

description: Require description formatting rules, such as: requiring the first letter be capitalized and/or ending with a period.

description: Require name to be lowercase.

description: Require version to follow semver.

description: Require all package.json properties to be in a specified order.

description: Ensure engineStrict is not present in package.json file.

description: Use the extends property to inherit rules from a shared configuration file/module.

type: string array

description: npm-package-json-lint rules are configurable. Use the rules object to specify what rules should be used and what severity level they should follow.

$ref: #/definitions/requiredNode

$ref: #/definitions/dataType

$ref: #/definitions/validValues

$ref: #/definitions/dependencies

$ref: #/definitions/format

$ref: #/definitions/packageJsonProperties

$ref: #/definitions/deprecated

title: JSON schema for npm-package-json-lint configuration files


bowerrc.json

type: boolean

description: The directory from which bower should run. All relative paths will be calculated according to this setting.

description: A file path to the Bower configuration file

type: string object

description: The registry config

format: uri

type: array string

description: An array of URLs pointing to read-only Bower registries. A string means only one. When looking into the registry for an endpoint, Bower will query these registries by the specified order.

description: The URL to use when registering packages.

description: The URL to use when publishing packages.

description: The proxy to use for http requests.

description: The proxy to use for https requests.

description: Sets the User-Agent for each request made.

type: number

description: The timeout to be used when making requests in milliseconds.

description: Whether or not to do SSL key validation when making requests via https.

type: object string

description: The CA certificates to be used, defaults to null. This is similar to the registry key, specifying each CA to use for each registry endpoint.

description: Enable or disable use of colors in the CLI output.

description: Where to store persistent data, such as cache, needed by bower.

description: Where to store temporary files and folders

description: Makes bower interactive, prompting whenever necessary

description: Identifies pluggable resolvers to be used for locating and fetching packages

description: Whitelists hosts which are known to support shallow cloning

description: Contains custom hooks used to trigger other automated tools

description: A script to run before install

description: A script to run after install

description: A script to run before uninstall

description: Bower will ignore these dependencies when resolving packages

title: JSON schema for .bowerrc files


first-timers.json

description: A bot that helps onboarding new open-source contributors.

title: Labels

description: Sets the labels if "first-timers-only" is not what you are looking for.

title: Label

title: Template

description: The path to your template, relative from the repository root.

title: Repository

description: Specify a different repository than where the problem is. The bot must be installed on the configured repository.

title: first-timers-bot


esquio.json

$ref: #/definitions/Product

$ref: #/definitions/Toggle

required: Name Enabled Toggles

$ref: #/definitions/Feature

required: Name Features

required: Type Parameters

$ref: #/definitions/Esquio

title: JSON schema for Esquio configuration files


tye-schema.json

title: Tye Configuration

description: Configuration file schema for Tye.

description: The application name.

description: Dockerhub username or hostname of remote registry. Used for tagging images.

description: Container engine.

enum: docker podman

description: The Kubernetes namespace to use.

description: The Docker network to use.

description: Configure the dashboard port used for `tye run`. Can be overridden using the `--port` CLI argument, and falls back to port 8000 if free, or a random port if 8000 is in use.

description: The application's ingresses.

$ref: #/definitions/ingress

description: Extensions to be added to tye.

$ref: #/definitions/extension

description: Indicates the solution file (.sln) or filter (.slnf) to use when building project-based services in watch mode. If omitted, those services will be built individually. Specifying the solution [filter] can help reduce repeated builds of shared libraries when in watch mode.

description: The application's services.

$ref: #/definitions/executable

$ref: #/definitions/external

$ref: #/definitions/azureFunction

$ref: #/definitions/image

$ref: #/definitions/dockerFile

$ref: #/definitions/project

$ref: #/definitions/repository

$ref: #/definitions/include

description: The binding name.

description: The binding port.

description: The port used when running inside a container.

description: The hostname for the binding.

description: The protocol used by the binding

description: Whether to auto-assign a port value.

description: The connection string.

description: Environment variable name.

description: Environment variable value.

required: name value

description: Build property name.

description: Build property name.

description: A named volume.

description: The local path.

description: The destination path within the container.

description: The service name. Must be unique per-application.

description: The directory path to the azure function.

description: Environment variables to use when launching.

$ref: #/definitions/env-var

description: Command-line arguments to use when launching.

description: Number of service replicas to create.

description: The bindings provided by the service.

$ref: #/definitions/binding

description: Optional path to the function host to be used when launching functions. Can point to either func.dll or the binary.

required: name azureFunction

description: The file path (or file name if on the system path) of an executable.

description: The working directory to use when launching.

description: Number of service replicas to create.

description: The bindings provided by the service.

required: name executable

description: Designates as service as external. External services will not be launched and can only provide bindings.

description: The bindings provided by the service.

description: The repository url which will be cloned.

description: The directory to clone the repository into.

required: name repository

description: Path to tye.yaml file which will be used in the application.

required: name include

description: Volumes to mount to the container.

$ref: #/definitions/volume

description: The name of a Docker image.

description: Number of service replicas to create.

description: The bindings provided by the service.

required: name image

description: Volumes to mount to the container.

description: The Dockerfile to use.

description: Build arguments to use when building the image.

description: The Dockerfile context to run docker build on.

description: Number of service replicas to create.

description: The bindings provided by the service.

description: The ingress name.

description: Bindings for the ingress in local development.

description: Rules for ingress routing.

description: The binding name.

description: The binding port.

description: The protocol used by the binding

description: The ip address the ingress listens on.

description: The service to route traffic when the rule matches.

description: The path prefix to match.

description: The hostname to match.

description: Whether to keep the path that was originally present or not after a prefix match.

description: The relative path to a .NET project file.

description: Build properties to use when launching or building a project.

description: Whether to build the project.

description: Number of service replicas to create.

description: The bindings provided by the service.

description: Extension name.


imgbotconfig.json

title: Limits the PRs from Imgbot to once a day, once a week, or once a month respectively. The default behavior is to receive Imgbot PRs as images require optimization.

enum: daily weekly monthly

title: Limits the images optimized by Imgbot by essentially ignoring them

title: Accepts the syntax for searchPattern on Directory.EnumerateFiles()

title: Opt in to use lossy compression algorithms. The default behaviour without this setting is loss less compression.

enum: true false

title: Opt in to also compress wiki repo. The default behaviour is opt out.

title: Can be used to limit the frequency of PRs Imgbot will open over time

title: JSON Schema for configuration for ImgBot


title: Definition

description: A workspace definition

$ref: #/definitions/Workspace

description: A profile definition

$ref: #/definitions/Profile

description: A table definition

$ref: #/definitions/Table

description: A classifier definition

$ref: #/definitions/Classifier

description: A function definition

$ref: #/definitions/Function

description: A plugin definition

$ref: #/definitions/Plugin

description: A workspace is a collection of one or more catalogs, schemas, tables, and resources, called workspace members, that are managed together.

required: edition name

description: The SDF edition, should always be 1 (for now)

description: The name of this workspace (defaults to the workspace directory name if not given) Name must be set for deployment.

description: A description of this workspace

description: The URL of the workspace source repository [defaults to 'none' if no repository is given]

description: The default output object store location, e.g. 's3://bucket/key/' where key is optional

description: An array of directories and filenames containing .sql and .sdf.yml files

$ref: #/definitions/IncludePath

description: An array of directories and filenames to be skipped when resolving includes

$ref: #/definitions/FilePath

description: An array of paths to other workspaces, i.e. .sql and .yml files

$ref: #/definitions/WorkspacePath

description: The dialect of this workspace. If not set, defaults to sdf dialect

$ref: #/definitions/Dialect

description: An array of paths to directories and files, which will be copied to the SDF service on deployment

description: Defines a default catalog [If not set, defaults to the directory of the workspace]

description: Defines a default schema [If not set, defaults to 'pub']

description: Defines the default profile [if not set, defaults to 'dbg']

description: Workspace defined by these set of files

description: An array of named values for setting SQL variables from your environment Ex. -dt: dt, used in SQL as @dt

$ref: #/definitions/Variable

description: An array of queries over the information schema that will be run on sdf describe and sdf deploy

$ref: #/definitions/CodeReportPath

$ref: #/definitions/CodeCheckPath

description: An array of attribute based access control queries over the information schema, current user and current job, that will be run on sdf build and sdf deploy

$ref: #/definitions/AccessControlPath

description: All file path should either be relative to the workspace, or absolute for an object store like AWS s3:// Note that an [IncludePath] specifies a catalog and schema scope for unqualified names (in effect for both creating and querying tables). See [IncludePath::default_catalog] and [IncludePath::default_schema].

description: A filepath

description: Defines a default catalog for unqualified names. If not set, defaults to the [Workspace] catalog.

description: Defines a default schema for unqualified names. If not set, defaults to the [Workspace] schema.

description: The dialect of the included files. If not set, defaults to the [Workspace] dialect.

description: Last modified of the file

$ref: #/definitions/SystemTime

enum: sdf presto bigquery redshift

description: A filepath

description: Last modified of the file

required: branch git path rev

description: The relative path from this workspace to the referenced workspace, for a Git repo, from the root of the depot to the workspace

description: The Git repo

description: the Git revision

description: the Git branch

description: SQL queries can be parameterized via variables of type varchar. A variable definition binds the variable to the provided value.

description: The name of the variable

description: The value of this variable (using sql/yaml literals)

required: name path

description: A filepath

description: Name of check (default filestem of path)

description: A description of this report

description: dialect

required: assert path

description: Assertion

$ref: #/definitions/CodeAssertion

description: A filepath

description: A description of this assertion

description: dialect

enum: exists not-exists

required: access name path

description: Grant access

$ref: #/definitions/Grant

description: A description of this access control rule

description: A filepath to a policy authored in .sql

enum: deny allow

description: Profiles provide a way to override the fields of a workspace, i.e. if a profile has set field X, then the workspace field X will be overridden by the profile field X.

description: A description of this workspace

description: The default dialect of this workspace. If not set, defaults to sdf dialect

description: Workspace defined by these set of files

description: A tables is either defined by given data (also called external table) or defined via a query.

description: An array of sql file names [Typically inferred]

description: ALl table dependencies (syntax: catalog.schema.table)

description: The columns of the schema: name, type, metadata

$ref: #/definitions/Column

description: The partitioning format of the table

$ref: #/definitions/Partition

description: The schedule of the table [expressed as cron]

description: The first date of the table [expressed by prefixes of RFC 33]

description: An array of classifier references

description: Array of reclassify instructions for changing the attached classifier labels

$ref: #/definitions/Reclassify

description: Lineage, a tagged array of column references

$ref: #/definitions/Lineage

description: The materialization scheme of this table

$ref: #/definitions/Materialization

description: Store data under this catalog.schema.table instead of the original name

description: Data is at this location

description: Store table in this format [only for external tables]

$ref: #/definitions/FileFormat

description: CSV data has a header [only for external tables]

description: CSV data is separated by this delimiter [only for external tables]

description: Json or CSV data is compressed with this method [only for external tables]

$ref: #/definitions/CompressionType

description: Table is defined by these .sql and/or .sdf files

description: The name of the column

description: A description of this column

description: The type of this column

description: The type of this column

description: An array of classifier references

description: The output column is computed by copying these upstream columns

description: The output column is computed by transforming these upstream columns

description: These upstream columns are indirectly used to produce the output (e.g. in WHERE or GROUP BY)

description: These functions were used to produce the output column

description: Target classifier

description: Expected source classifier

description: A partition is a table column, used to describe to which partition this row belongs to

description: The name of the partition column

description: A description of the partition column

description: The format of the partition column [use strftime format for date/time] See (guide)[https://docs.sdf.com/guide/schedules]

description: All derived tables are cached by default

description: External tables must be explicitly marked When using 'Create external table` SQL syntax

description: View

description: Ephemeral

description: Recursive warehouse tables must be  explicitly  marked

description: Store table data in these formats

description: Compress table data using these methods

description: BZIP2 Compression (.bz2)

description: GZIP Compression (.gzip)

description: None, (default)

description: A classifier defines the labels that can be attached to columns or a table.

description: The name of the classifier type

description: A description of this classifier type

description: Named classifier labels

description: scope of the classifier: table or column

description: cardinality of the classifier: zero-or-one, one or zero-or-many

description: does the classifier propagate from scope to scope or is it a one scope marker

description: Classifier defined by these set of .sdf files

description: A classifier element is a scoped classifier label (e.g. the element PII belongs to the classifier scope data)

description: The name of the label, use "*" to allow arbitrary strings as labels

description: A description of this classifier element

description: A function block defines the signature for user defined

description: The name of the function [syntax: [[catalog.]schema].function]

description: The generic type bounds

description: The dialect that provides this function

description: A description of this function

description: Arbitrary number of arguments of an common type out of a list of valid types

description: The function kind

description: The arguments of this function

description: The arguments of this function

description: The results of this function (can be a tuple)

description: The generic type bounds

description: volatility - The volatility of the function.

description: example - Example use of the function (tuple with input/output)

description: cross-link - link to existing documentation, for example: https://prestodb.io/docs/current/functions/datetime.html#truncation-function

description: Function defined by these set of .sdf files

description: All arguments have the same types

description: All even arguments have one type, odd arguments have another type

description: A function parameter

description: The name of the parameter

description: A description of this parameter

description: The datatype of this parameter

description: The nullability of this column

description: An array of classifier references

description: The required constant value of this parameter

description: The parameter may appear as identifier, without quote

description: A function parameter

description: The name of the parameter

description: A description of this parameter

description: The datatype of this parameter

description: An array of classifier references

description: A function's volatility, which defines the functions eligibility for certain optimizations

description: Pure - An pure function will always return the same output when given the same input.

description: Stable - A stable function may return different values given the same input across different queries but must return the same value for a given input within a query.

description: Volatile - A volatile function may change the return value from evaluation to evaluation. Multiple invocations of a volatile function may return different results when used in the same query.

description: The sql string corresponding to the input of this example

description: The output corresponding to running the input string

description: The name of the plugin [e.g.: pyspark]

description: Full path to the binary [e.g.: /usr/bin/python3]

description: File extension to scan in the includes directories; must be unique [e.g.: .py]

description: Format of the output files; must be known to SDF [e.g.: spark-lp-json]


role-arg-spec.json

enum: str list dict bool int float path raw jsonarg json bytes bits

$ref: #/$defs/option

required: description ref

required: description link name

title: Entry Point

markdownDescription: xxx

description: Detailed explanation of what this option does. It should be written in full sentences.

$ref: #/$defs/datatype

description: The name of the option/argument.

title: Option

markdownDescription:
Add entry point, usually `main`.
See [role-argument-validation](https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html#role-argument-validation)

title: Ansible Role Argument Specs Schema


stryker-core.json

title: StrykerOptions

description: JSON schema for the Stryker Mutator configuration file

title: CommandRunnerOptions

description: The command to test each mutant. For example "npm run mocha". Defaults to "npm test".

default: npm test

title: LogLevel

enum: off fatal error warn info debug trace

tsEnumNames: Off Fatal Error Warning Information Debug Trace

title: CoverageAnalysis

enum: off all perTest

title: ReportType

enum: full mutationScore

tsEnumNames: Full MutationScore

title: ClearTextReporterOptions

description: Indicates whether or not to use color coding in output.

description: Enable emojis in your clear text report (experimental).

description: Indicates whether or not to log which tests were executed for a given mutant.

description: Indicates the maximum amount of test to log when `logTests` is enabled

title: DashboardOptions

description: Indicates which project to use if the "dashboard" reporter is enabled.

description: Indicates which version to use if the "dashboard" reporter is enabled.

description: Indicates which module to use if the "dashboard" reporter is enabled.

description: Indicates the base url of the stryker dashboard.

description: Indicates wether to send a full report (inc. source code and mutant results) or only the mutation score.

$ref: #/definitions/reportType

default: full

title: EventRecorderOptions

description: The base dir to write the events to

default: reports/mutation/events

title: HtmlReporterOptions

description: The `fileName` of the html report.

title: JsonReporterOptions

description: The relative filename for the json report.

title: MutationScoreThresholds

$ref: #/definitions/percentage

description: Override the default babel plugins Stryker uses to parse your JavaScript files. The default list of plugins is extensive and normally doesn't need overriding. Stryker also loads your babel plugins by default (if you have them). If Stryker's default babel plugins conflicts with your plugins, try to override this list with an empty array.

title: WarningOptions

description: decide whether or not to log warnings when additional stryker options are configured

description: decide whether or not to log warnings when a preprocessor error occurs. For example, when the disabling of type errors fails.

description: decide whether or not to log warnings when a configuration options are unserializable. For example, using a `/regex/` or `function` in your configuration options.

description: decide whether or not to log warnings when Stryker detects a slow part of mutation that can be sped up by changing some configuration. For example using `--ignoreStatic`.

description: The 'allowConsoleColors' value indicates whether Stryker should use colors in console.

description: Configure a build command to run after mutating the code, but before mutants are tested. This is generally used to transpile your code before testing. Only configure this if your test runner doesn't take care of this already and you're not using just-in-time transpiler like `babel/register` or `ts-node`.

examples:
tsc -b
babel src --out-dir lib
npm run build

description: Enable checker plugins here. A checker plugin will be invoked for each mutant before it is run in a test runner. It can check to see of a given mutant is valid, by for example validate that it won't result in a type error

description: Configure arguments to be passed as exec arguments to the checker child process(es). For example, running Stryker with `--concurrency 1 --checkerNodeArgs --inspect-brk` will allow you to debug the checker child process. See `execArgv` of [`child_process.fork`](https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options)

description: Set the concurrency of workers. Stryker will always run checkers and test runners in parallel by creating worker processes (note, not `worker_threads`). This defaults to `n-1` where `n` is the number of logical CPU cores available on your machine, unless `n <= 4`, in that case it uses `n`. This is a sane default for most use cases.

description: Options used by the command test runner. Note: these options will only be used when the command test runner is activated (this is the default)

$ref: #/definitions/commandRunnerOptions

$ref: #/definitions/coverageAnalysis

description:
Indicates which coverage analysis strategy to use. During mutation testing, Stryker will try to only run the tests that cover a particular mutant.

'perTest': Analyse coverage per test.
'all': Analyse the coverage for the entire test suite.
'off' (default): Don't use coverage analysis

default: perTest

description: The options for the clear text reporter.

$ref: #/definitions/clearTextReporterOptions

description: The options for the dashboard reporter.

$ref: #/definitions/dashboardOptions

description: Execute the initial test run only without doing actual mutation testing. Dry run only will still mutate your code before doing the dry run without those mutants being active, thus can be used to test that StrykerJS can run your test setup. This can be useful, for example, in CI pipelines.

description: The options for the event recorder reporter.

$ref: #/definitions/eventRecorderOptions

description: A comma separated list of patterns used for specifying which files need to be ignored. This should only be used in cases where you experience a slow Stryker startup, because too many (or too large) files are copied to the sandbox that are not needed to run the tests. For example, image or movie directories. Note: This option will have NO effect when using the `--inPlace` option. The directories `node_modules`, `.git` and some others are always ignored. Example: `--ignorePatterns dist`. These patterns are ALWAYS ignored: [`node_modules`, `.git`, `/reports`, `*.tsbuildinfo`, `/stryker.log`, `.stryker-tmp`]. Because Stryker always ignores these, you should rarely have to adjust the `ignorePatterns` setting at all. This is useful to speed up Stryker by ignoring big directories/files you might have in your repo that has nothing to do with your code. For example, 1.5GB of movie/image files. Specify the patterns to all files or directories that are not used to run your tests and thus should NOT be copied to the sandbox directory for mutation testing. Each patterns in this array should be a [glob pattern](#usage-of-globbing-expressions-on-options). If a glob pattern starts with `/`, the pattern is relative to the current working directory. For example, `/foo.js` matches to `foo.js` but not `subdir/foo.js`. However to SELECT specific files TO BE mutated, you better use `--mutate`.

description: Ignore static mutants. Static mutants are mutants which are only executed during the loading of a file. This means that Stryker has to reload the entire environment in order to test the mutant AND has to run all tests. Therefore, it might make sense to ignore static mutants.

description: Enable 'incremental mode'. Stryker will store results in a file and use that file to speed up the next --incremental run

description: Specify the file to use for incremental mode.

description: Run all mutants, even if --incremental is provided and an incremental file exists. Can be used to force a rebuild of the incremental file.

description: Set the log level that Stryker uses to write to the "stryker.log" file

$ref: #/definitions/logLevel

default: off

description:
Determines whether or not Stryker should mutate your files in place. Note: mutating your files in place is generally not needed for mutation testing, unless you have a dependency in your project that is really dependent on the file locations (like "app-root-path" for example).

When `true`, Stryker will override your files, but it will keep a copy of the originals in the temp directory (using `tempDirName`) and it will place the originals back after it is done. Also with `true` the `ignorePatterns` has no effect any more.

When `false` (default) Stryker will work in the copy of your code inside the temp directory.

description: Set the log level that Stryker uses to write to the console.

default: info

description: [DEPRECATED please use "concurrency" instead]. Specifies the maximum number of concurrent test runners to spawn. Mutation testing is time consuming. By default, Stryker tries to make the most of your CPU's, by spawning as many test runners as you have CPU cores (`Number.MAX_SAFE_INTEGER`).

description: Restart each test runner worker process after `n` runs. Not recommended unless you are experiencing memory leaks that you are unable to resolve. Configuring `0` here means infinite reuse.

description:
With `mutate` you configure the subset of files or just one specific file to be mutated. These should be your _production code files_, and definitely not your test files.
(Whereas with `ignorePatterns` you prevent non-relevant files from being copied to the sandbox directory in the first place)
The default will try to guess your production code files based on sane defaults. It reads like this:
- Include all js-like files inside the `src` or `lib` dir
- Except files inside `__tests__` directories and file names ending with `test` or `spec`.
If the defaults are not sufficient for you, for example in a angular project you might want to
 **exclude** not only the `*.spec.ts` files but other files too, just like the default already does.
It is possible to specify exactly which code blocks to mutate by means of a _mutation range_. This can be done postfixing your file with `:startLine[:startColumn]-endLine[:endColumn]`. Example: src/index.js:1:3-1:5

description: Configure how Stryker mutates your code.

$ref: #/definitions/mutatorDescriptor

enum: npm yarn pnpm

description: The package manager Stryker can use to install missing dependencies.

description: With 'plugins', you can add additional Node modules for Stryker to load (or require). By default, all node_modules starting with @stryker-mutator/* will be loaded, so you would normally not need to specify this option. These modules should be installed right next to stryker. For a current list of plugins, you can consult 'npm' or 'stryker-mutator.io.'

description: A list of additional plugins you want Stryker to load (`require`) without overwriting the (default) `plugins`.

description: With reporters, you can set the reporters for stryker to use.

default: clear-text progress html

description: The options for the html reporter

$ref: #/definitions/htmlReporterOptions

description: The options for the json reporter

$ref: #/definitions/jsonReporterOptions

description: Set to 'true' to disable type checking, or 'false' to enable it. For more control, configure a pattern that matches the files of which type checking has to be disabled. This is needed because Stryker will create (typescript) type errors when inserting the mutants in your code. Stryker disables type checking by inserting `// @ts-nocheck` atop those files and removing other `// @ts-xxx` directives (so they won't interfere with `@ts-nocheck`). The default setting allows these directives to be stripped from all JavaScript and friend files in `lib`, `src` and `test` directories.

description: The 'symlinkNodeModules' value indicates whether Stryker should create a symbolic link to your current node_modules directory in the sandbox directories. This makes running your tests by Stryker behave more like your would run the tests yourself in your project directory. Only disable this setting if you really know what you are doing.

description: Choose a different temp dir that Stryker uses for mutation testing. This directory will contain copies of your source code during a mutation test run. It will be created if it not exists and is *entirely deleted* after a successful run, so change this with caution.

default: .stryker-tmp

description:
Choose whether or not to clean the temp dir (which is ".stryker-tmp" inside the current working directory by default).
 - false: Never delete the temp dir;
 - true: Delete the tmp dir after a successful run;
 - "always": Always delete the temp dir, regardless of whether the run was successful.

description: With 'testRunner' you specify the test runner that Stryker uses to run your tests. The default value is command. The command runner runs a configurable bash/cmd command and bases the result on the exit code of that program (0 for success, otherwise failed). You can configure this command via the config file using the 'commandRunner: { command: 'npm run mocha' }'. It uses 'npm test' as the command by default.

default: command

description: Configure arguments to be passed as exec arguments to the test runner child process. For example, running Stryker with `--timeoutMS 9999999 --concurrency 1 --testRunnerNodeArgs --inspect-brk` will allow you to debug the test runner child process. See `execArgv` of [`child_process.fork`](https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options)

description: Specify the thresholds for mutation score.

$ref: #/definitions/mutationScoreThresholds

description: Configure the allowed timeout deviation relative to the time of a normal test run. Tweak this if you notice that mutants are prone to creating slower code, but not infinite loops (for that, use `timeoutMS`)

description: Configure an absolute timeout deviation. Tweak this if you run Stryker on a busy machine and you need to wait longer to make sure that the code indeed entered an infinite loop.

description: Configure an absolute timeout for the initial test run. (It can take a while, therefore we use minutes as time unit.)

description: Configure the (root) tsconfig file for typescript projects. This will allow Stryker to rewrite the `extends` and `references` settings in this and related tsconfig files in your sandbox. Defaults to `tsconfig.json`. This setting is also used when you enable the `@stryker-mutator/typescript-checker plugin

description: Enable or disable certain warnings

description: Disables the default of bailing after first failing test. When true runs all tests covering a mutant. Useful when the subject under test is not completely isolated by mocks and you want to know which tests are killing the mutants. This will impact performance.

description: Allows stryker to exit without any errors in cases where no tests are found


drupal-links-action.json

title: The static title for the local action

title: The translation context for the title value.

title: The route name used to generate a link

title: Route parameters for generating a link

title: The weight of the local action

title: Array of link options

title: The route names where this local action appears

title: Class for local action implementations

title: Deriver class

title: Cache tags

title: JSON schema for Drupal action links file


sprite.json

description: Schema for image sprite generation files

description: Define custom CSS declarations to inject into the generated stylesheet.

description: A custom CSS declaration (property: value).

type: string number

description: The image resolution of the generated image sprite

description: An array of file paths relative to this document. The name must be unique.

description: A source image for the sprite.

description: Optimizes the generated image either lossy or lossless. Requires the "Image Optimizer" extension for Visual Studio

enum: lossless lossy none

default: lossless

description: The orientation of the individual images inside the generated sprite.

enum: horizontal vertical

default: vertical

description: Output format of the generated image sprite.

description: The padding arround each individual image in the sprite. The value is in pixels.

description: Add any path root in front of the generated. Example: "/images/"

description: Define stylesheets (css, less, sass) to be generated as part of the sprite generation process.

enum: none css less scss styl


description: Freifunk Community API 0.5.2

title: City

description: Name of the city

title: Country

description: Your country, list has been taken from http://countrylist.net/de/

enum: AF AX AL DZ AS AD AO AI AQ AG AR AM AW AC AU AT AZ BS BH BD BB BY BE BZ BJ BM BT BO BA BW BV BR IO BN BG BF BI KH CM CA IC CV KY CF TD CL CN CX CC CO KM CG CD CK CR CI HR CU CY CZ DK DG DJ DM DO EC EG SV GQ ER EE ET EU FK FO FJ FI FR GF PF TF GA GM GE DE GH GI GR GL GD GP GU GT GG GN GW GY HT HM VA HN HK HU IS IN ID IR IQ IE IM IL IT JM JP JE JO KZ KE KI KP KR KW KG LA LV LB LS LR LY LI LT LU MO MK MG MW MY MV ML MT MH MQ MR MU YT MX FM MD MC MN ME MS MA MZ MM NA NR NP NL AN NC NZ NI NE NG NU NF MP NO OM PK PW PS PA PG PY PE PH PN PL PT PR QA RE RO RU RW SH KN LC PM VC WS SM ST SA NT SN CS SC SL SG SK SI SB SO ZA GS SU ES LK SD SR SJ SZ SE CH SY TW TJ TZ TH TL TG TK TO TT TA TN TR TM TC TV UG UA AE GB US UY UZ VU VE VN VG VI WF EH YE ZM ZW

description: The address of the place you meet

title: Name of your place

description: The name of the place you meet

title: Street

description: The street address of your meeting place

title: ZIP

description: The zip code of your meeting place

title: Latitude

description: Lattitude of your city in decimal degrees

title: Longitude

description: Longitude of your city in decimal degrees

required: lat lon

title: Email

format: email

title: Phone

title: API

description: The Freifunk Community API version you use

title: Name

description: The name of your community

title: Metacommunity

description: The name of your metacommunity, if your local community belongs to a bigger one

title: Primary Location

description: Position data such as a postal address or geographic coordinates

$ref: #/definitions/city

$ref: #/definitions/country

$ref: #/definitions/address

$ref: #/definitions/geoCode

title: Additional Locations

description: Add some more locations where your community is active.

title: Location

required: city geoCode

$ref: #/definitions/email

title: Email

description: Email address to which other people can contact your community (user@domain.com)

title: facebook

description: URL to your community's facebook account (https://facebook.com/...)

title: identica

description: URL to your community's identica account (https://identi.ca/...)

title: IRC

description: Your community's ICR channel; starts with irc://

title: Jabber

description: A jabber account someone reads (account@jabberserver.tld)

title: Mailinglist

description: The email address (user@domain.com) of your mailing list or a link to the mailinglist info page (http{s}://...)

title: Google+

description: URL to your community's g+ account (https://plus.google.com/...)

title: Matrix

description: URL to your community's matrix channel (https://matrix.to/#/!...)

title: Mastodon

$ref: #/definitions/url

description: URL to your community's mastodon profile (https://...)

title: Twitter

description: Your community's Twitter name (starts with @)

title: Webform

description: URL to your community's contact form (http{s}://...)

$ref: #/definitions/phone

title: Phone

description: If your community has a phone number (e.g. +49 1234 567890 based on the E.123 notation)

title: HomePage

description: The main website (http{s}://...)

description: These are lifetime events something like date of birth (and rebirth :-) of your community or other important milestones

title: Description

description: Description of your lifetime event

title: Timestamp

format: date

description: ISO 8601 timestamp of the event's date (format yyyy-mm-dd)

title: URL

description: URL to details of this timeline-element

title: Feeds

description: Feeds you provide your community

title: Feed name

description: Name of the feed

title: Feed category

description: Category of the feed like blog entries, calendars, forum messages, wiki articles, ...

enum: blog forum ics podcast wiki others

title: Feed Type

description: Type of the feed like RSS, Atom, XML

title: URL

description: URL of the feed

title: States

description: A collection of status-related data. Actual open/closed status, icons, last change timestamp etc.

title: Active Nodes

description: Number of active nodes. This field is predestined to be updated regularly, please see sample solutions for Gluon or OLSR

title: Last Change

format: date-time

description: At what ISO 8601 timestamp has your community status lastly changed?

title: Message

description: A free-form string something like 'open for public', 'members only' or whatever you want it to be)

title: Description

description: Describe your community in a few lines

title: Focus

description: What's the focus of your local community?

title: option

enum:
infrastructure/backbone
Public Free Wifi
Social Community Building
Local services and content
Free internet access

title: Nodes

description: Maps of nodes or topology your community provides

title: node

title: URL of the map

description: The URL where the map is located

title: interval

description: How often the map will be refreshed

title: map techincal type

description: The kind of map is used

enum: ffmap ffsomething olsr-dot openwifimap netmon libremap nodewatcher kml nodelist meshviewer hopglass

title: Maptype

enum: geographical structural list/status

title: Services

description: Services Provided by your community

title: Service Name

description: Name of your service (e.g. jabber...)

title: Service Description

description: Describe your service

title: External URI

description: URI to use your service from the internet

title: Internal URI

description: URI to use your service from Freifunk or icvpn-networks

title: Support for your community

title: Supporting Club

title: Club Name

description: Name of the Club

title: Street

description: Address - Street

title: ZIP

description: Address - ZIP

title: HomePage

description: The club's website (http{s}://...)

description: Email address to contact the club (user@domain.com)

title: Board Members

description: Who are the board members of the club?

title: Name

title: Donations

title: Bank Account

title: IBAN

title: BIC

title: Usage of the donations

description: Please use this string as transfer-purpose to define a special usage of your donation.

title: Campaigns

title: campaign

title: Campaign Providers

description: Where do you host your donations?

enum: betterplace boost

title: Project ID

description: ID of your project, Betterplace-IDs are multiple digits and can be found within the URL

title: Number of Projects

description: Number of projects supported by your Community

title: URL of your page

description: A link to a web site where people can find an overview over your projects

title: Contact Email

description: Please provide an email address to contact you on refugees and social projects

title: Privacy Policy

title: Privacy Policy URL

description: URL to your privacy policy description

description: Technical details of your community's Freifunk implementation

title: Firmware download

description: Link to your firmware images

title: Firmware Document

description: Link to your firmware docs

title: VPN Access

description: How to access your VPN services

title: VPN Registration URL

description: link to your website to request a new VPN key

title: Organizational Restrictions

description: Are there any organizational restrictions when using/installing your firmware?

title: Technical Restriction

description: Are there any technical restrictions like hardware?

title: Firmware Name

description: Name of your firmware

title: DNS Servers

description: DNS servers for domains used by your community

title: dns

title: Domain Name

description: The domain name (e.g. ffhh, ffol)

title: Nameserver

description: Nameservers servings zones of your domain

description: Networks used by your community

title: IPv6 networks

description: IPv6 networks used by your community

title: ipv6 network object

description: IPv6 network network (e.g.2620:0:2d0:200::7/32) in CIDR notation

description: IPv4 networks used by your community

title: ipv4 network object

description: IPv4 network name (e.g. 10.w.x.y/z) in CIDR notation

title: Routing protocols

description: Routing protocols used within your community

title: option

title: Legal Issues

description: What do you use to handle legal issues, e.g. the German Störerhaftung or restrictions in your country?

title: option

enum: nothing vpnnational vpninternational zappscript p2pblock splashpage termsconditions anonymizer institutions

title: Updatemode

description: How do you deploy firmware updates?

title: option

required: name location contact url state techDetails


nswag.json

$ref: #/definitions/webApiToSwagger

$ref: #/definitions/swaggerToTypeScriptClient

$ref: #/definitions/swaggerToCSharpClient

$ref: #/definitions/swaggerToCSharpController

enum: Default CamelCase SnakeCase

enum: Integer String CamelCaseString

enum: MultipleClientsFromOperationId MultipleClientsFromPathSegments SingleClientFromOperationId SingleClientFromPathSegments

$ref: #/definitions/clientGenerator

enum: JQueryCallbacks JQueryPromises AngularJS Angular Fetch Aurelia

enum: Promise QPromise

enum: Http HttpClient

enum: OpaqueToken InjectionToken

enum: Interface Class KnockoutClass

$ref: #/definitions/swaggerGenerator

$ref: #/definitions/codeGenerators


title: RuleType

description: An enumeration.

enum: refactoring suggestion comment hover

title: PythonVersion

title: Major

title: Minor

required: major minor

title: RuleSettingsConfig

title: Enable

title: Disable

description: A list of rule IDs Sourcery will never suggest.

default: refactoring suggestion comment

$ref: #/definitions/RuleType

title: Python Version

description: A string specifying the lowest Python version your project supports. Sourcery will not suggest refactorings requiring a higher Python version.

$ref: #/definitions/PythonVersion

title: RuleLanguage

description: An enumeration.

enum: python java javascript typescript

title: PathsConfig

title: Include

title: Exclude

title: MatchRuleTestConfig

title: Match

title: Expect

title: NoMatchRuleTestConfig

title: No-Match

title: RuleConfig

title: Id

title: Description

title: Pattern

default: python

$ref: #/definitions/RuleLanguage

title: Replacement

title: Condition

title: Explanation

$ref: #/definitions/PathsConfig

title: Tests

$ref: #/definitions/MatchRuleTestConfig

$ref: #/definitions/NoMatchRuleTestConfig

title: Tags

required: id description pattern

title: MetricsConfig

title: Quality Threshold

title: RequestReview

title: Origin

title: Forked

title: GitHubConfig

title: Labels

title: Ignore Labels

title: Request Review

default: author

$ref: #/definitions/RequestReview

title: Sourcery Branch

title: CloneDetectionConfig

title: Min Lines

title: Min Duplicates

title: Identical Clones Only

title: ProxyConfig

title: Url

title: Ssl Certs File

title: No Ssl Verify

title: Version

description: The schema version of this config file

title: Ignore

description: A list of paths or files which Sourcery will ignore.

title: Rule Settings

rule_types: refactoring suggestion comment

$ref: #/definitions/RuleSettingsConfig

title: Rules

description: A list of custom rules Sourcery will include in its analysis.

$ref: #/definitions/RuleConfig

title: Rule Tags

description: Additional rule tags.

title: Metrics

$ref: #/definitions/MetricsConfig

title: Github

review_or_request_review: author

$ref: #/definitions/GitHubConfig

title: Clone Detection

$ref: #/definitions/CloneDetectionConfig

title: Proxy

$ref: #/definitions/ProxyConfig

title: Sourcery YAML Schema


catalog-info.json

description: An API describes an interface that can be exposed by a component. The API can be defined in different formats, like OpenAPI, AsyncAPI, GraphQL, gRPC, or other formats.

kind: API

artist-api

description: Retrieve artist details

product_name: Random value Generator

type: openapi

lifecycle: production

owner: artist-relations-team

[System] artist-engagement-portal

required: type lifecycle owner definition

description: The type of the API definition.

examples: openapi asyncapi graphql grpc

description: The lifecycle state of the API.

examples: experimental production deprecated

description: An entity reference to the owner of the API.

description: An entity reference to the system that the API belongs to.

description: The definition of the API, based on the format defined by the type.

description: Interprets the contents of the referenced file as plain text and embeds it as a string.

description: Interprets the contents of the referenced file as JSON and embeds the parsed structure.

description: Interprets the contents of the referenced file as YAML and embeds the parsed structure.

description: A Component describes a software component. It is typically intimately linked to the source code that constitutes the component, and should be what a developer may regard a "unit of software", usually with a distinct deployable or linkable artifact.

kind: Component

LoremService

description: Creates Lorems like a pro.

type: service

owner: tools

required: type lifecycle owner

description: The type of component.

examples: service website library

description: The lifecycle state of the component.

description: An entity reference to the owner of the component.

description: An entity reference to the system that the component belongs to.

description: An entity reference to another component of which the component is a part.

description: An array of entity references to the APIs that are provided by the component.

description: An array of entity references to the APIs that are consumed by the component.

description: An array of references to other entities that the component depends on to function.

description: A Domain groups a collection of systems that share terminology, domain models, business purpose, or documentation, i.e. form a bounded context.

kind: Domain

artists

description: Everything about artists

description: A group describes an organizational entity, such as for example a team, a business unit, or a loose collection of people in an interest group. Members of these groups are modeled in the catalog as kind User.

kind: Group

infrastructure

description: The infra business unit

type: business-unit

displayName: Infrastructure

parent: ops

children: backstage other

required: type children

description: The type of group. There is currently no enforced set of values for this field, so it is left up to the adopting organization to choose a nomenclature that matches their org hierarchy.

examples: team business-unit product-area root

description: Optional profile information about the group, mainly for display purposes. All fields of this structure are also optional. The email would be a group email of some form, that the group may wish to be used for contacting them. The picture is expected to be a URL pointing to an image that's representative of the group, and that a browser could fetch and render on a group page or similar.

description: A simple display name to present to users.

description: An email where this entity can be reached.

description: The URL of an image that represents this entity.

description: The immediate parent group in the hierarchy, if any. Not all groups must have a parent; the catalog supports multi-root hierarchies. Groups may however not have more than one parent. This field is an entity reference.

description: The immediate child groups of this group in the hierarchy (whose parent field points to this group). The list must be present, but may be empty if there are no child groups. The items are not guaranteed to be ordered in any particular way. The entries of this array are entity references.

examples: backstage other

description: The users that are members of this group. The entries of this array are entity references.

description: A location is a marker that references other places to look for catalog data.

kind: Location

type: url

description: The single location type, that's common to the targets specified in the spec. If it is left out, it is inherited from the location type that originally read the entity data.

description: A single target as a string. Can be either an absolute path/URL (depending on the type), or a relative path such as ./details/catalog-info.yaml which is resolved relative to the location of this Location entity itself.

description: A list of targets as strings. They can all be either absolute paths/URLs (depending on the type), or relative paths such as ./details/catalog-info.yaml which are resolved relative to the location of this Location entity itself.

description: A resource describes the infrastructure a system needs to operate, like BigTable databases, Pub/Sub topics, S3 buckets or CDNs. Modelling them together with components and systems allows to visualize resource footprint, and create tooling around them.

kind: Resource

artists-db

description: Stores artist details

type: database

[System] artist-engagement-portal

required: type owner

description: The type of resource.

examples: database s3-bucket cluster

description: An entity reference to the owner of the resource.

description: An array of references to other entities that the resource depends on to function.

description: An entity reference to the system that the resource belongs to.

description: A system is a collection of resources and components. The system may expose or consume one or several APIs. It is viewed as abstraction level that provides potential consumers insights into exposed features without needing a too detailed view into the details of all components. This also gives the owning team the possibility to decide about published artifacts and APIs.

kind: System

artist-engagement-portal

description: Handy tools to keep artists in the loop

domain: artists

description: An entity reference to the domain that the system belongs to.

description: A Template describes a scaffolding task for use with the Scaffolder. It describes the required parameters as well as a series of steps that will be taken to execute the scaffolding task.

kind: Template

react-ssr-template

title: React SSR Template

description: Next.js application skeleton for creating isomorphic web applications.

type: website

required: name description

title: Name

description: Unique name of the component

title: Description

description: Description of the component

Fetch

url: ./template

Publish to GitHub

repoUrl: {{ parameters.repoUrl }}

if: {{ parameters.repoUrl }}

description: The type of component created by the template. The software catalog accepts any type value, but an organization should take great care to establish a proper taxonomy for these. Tools including Backstage itself may read this field and behave differently depending on its value. For example, a website type component may present tooling in the Backstage interface that is specific to just websites.

description: The JSONSchema describing the inputs for the template.

description: A list of separate forms to collect parameters.

description: A list of steps to execute.

description: A description of the step to execute.

description: The ID of the step, which can be used to refer to its outputs.

description: The name of the step, which will be displayed in the UI during the scaffolding process.

description: The name of the action to execute.

description: A templated object describing the inputs to the action.

description: A templated condition that skips the step when evaluated to false. If the condition is true or not defined, the step is executed. The condition is true, if the input is not `false`, `undefined`, `null`, `""`, `0`, or `[]`.

description: A templated object describing the outputs of the scaffolding task.

description: A list of external hyperlinks, typically pointing to resources created or updated by the template

description: A url in a standard uri format.

description: An entity reference to an entity in the catalog.

description: A user friendly display name for the link.

description: A key representing a visual icon to be displayed in the UI.

description: The user (or group) owner of the template

description: A user describes a person, such as an employee, a contractor, or similar. Users belong to Group entities in the catalog. These catalog user entries are connected to the way that authentication within the Backstage ecosystem works. See the auth section of the docs for a discussion of these concepts.

description: Optional profile information about the user, mainly for display purposes. All fields of this structure are also optional. The email would be a primary email of some form, that the user may wish to be used for contacting them. The picture is expected to be a URL pointing to an image that's representative of the user, and that a browser could fetch and render on a profile page or similar.

description: An email where this user can be reached.

description: The URL of an image that represents this user.

description: The list of groups that the user is a direct member of (i.e., no transitive memberships are listed here). The list must be present, but may be empty if the user is not member of any groups. The items are not guaranteed to be ordered in any particular way. The entries of this array are entity references.

description: The parts of the format that's common to all versions/kinds of entity.

LoremService

description: Creates Lorems like a pro.

description: The version of specification format for this particular entity that this is written against.

description: The high level entity type being described.

examples: API Component Domain Group Location Resource System Template User

description: Metadata fields common to all versions/kinds of entity.

description: A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.

description: An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.

description: A positive nonzero number that indicates the current generation of data for this entity; the value is incremented each time the spec changes. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations.

description: The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.

description: The namespace that the entity belongs to.

description: A display name of the entity, to be presented in user interfaces instead of the name property, when available.

description: A short (typically relatively few words, on one line) description of the entity.

description: Key/value pairs of identifying information attached to the entity.

description: Key/value pairs of non-identifying auxiliary information attached to the entity.

description: A list of single-valued strings, to for example classify catalog entities in various ways.

description: A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.

description: A url in a standard uri format.

description: A user friendly display name for the link.

description: The specification data describing the entity itself.

description: The relations that this entity has with other entities.

description: Common definitions to import from other schemas

description: A reference by name to another entity.

description: The kind field of the entity.

description: The metadata.namespace field of the entity.

description: The metadata.name field of the entity.

description: A directed relation from one entity to another.

description: The type of relation.

description: The current status of the entity, as claimed by various sources.

description: A specific status item on a well known format.

description: The status level / severity of the status item.

description: A brief message describing the status, intended for human consumption.

description: An optional serialized error object related to the status.

description: A status level / severity.

description: A serialized error object.

description: The type name of the error

description: The message of the error

description: An error code associated with the error

description: An error stack trace


nuget-project.json

$ref: #/definitions/dependencies

type: string

description: A list of dependencies.

default: default

enum: default build

description: The frameworks on which your project will run.

$ref: #/definitions/configType

description: The Operating System and Architectures on which your application will be running.

description: A list of supported target frameworks.

description: A supported target framework.

title: JSON schema for NuGet project.json files


as-code.latest.schema.json

title: JSON Schema for NeoLoad as-code files

xrequired:
name
because neoload files can be partial

$ref: #/definitions/common/name

$id: #root/includes

title: Includes

$ref: #/definitions/common/text

$id: #root/variables

title: Variables

$ref: #/definitions/variables/constant

$ref: #/definitions/variables/file

$ref: #/definitions/variables/counter

$ref: #/definitions/variables/javascript

$id: #root/servers

title: Servers

$ref: #/definitions/server

title: SLA Profiles

$ref: #/definitions/sla

$id: #root/populations

title: Populations

$ref: #/definitions/populations/population

$id: #root/scenarios

title: Scenarios

$ref: #/definitions/scenario

title: User_paths

$id: #/definitions/common/text

title: Text

title: Positive Number

type: integer

$id: #/definitions/common/duration

title: Duration

$ref: #/definitions/common/time

$ref: #/definitions/common/iterations

title: variation_policy.stop_after values

title: Start after

$id: #/definitions/common/time

title: Time

$id: #/definitions/common/iterations

title: Iterations

pattern: ^(\d+ iterations)$

title: Name

title: Url

default: global

enum: local global unique

enum: sequential random any

$id: #/definitions/variables/generic

$id: #/definitions/variables/constant

title: Constant

$ref: #/definitions/variables/generic

$id: #/definitions/variables/file

title: File

$id: #/definitions/variables/counter

title: Counter

xrequired: start end increment

title: Random Number

xrequired: min max

$id: #/definitions/variables/javascript

title: Javascript

$id: #/definitions/server

title: Server

xrequired: name host

$id: #root/servers/items/scheme

enum: http https

$ref: #/definitions/authentication/basic

$ref: #/definitions/authentication/ntlm

xrequired: login password

title: Basic Authentication

title: NTLM Authentication

title: Negotiate Authentication

title: SLA Profile

title: Thresholds

title: Threshold

title: Population

value: why do we need the substructure 'name' to denote a string list?

title: Constant Load

title: Ramp-up Load

title: Peaks Load

title: Peak Phase

title: Scenario

title: Scenario Populations

title: User Path

title: Containers

title: Steps

transaction

title: Action: Transaction

title: Steps

title: Action: HTTP/s Request

title: Action: Delay

title: Action: Think Time

title: Action: Javascript

title: Action: If

xcomments: like GWBSR said: 'aint gonna do it', at least not this commit


component-detection-manifest.json

$ref: #/definitions/CGManifest

$ref: #/definitions/Registration

required: registrations version

title: CGManifest

type: object

title: Registration

$ref: #/definitions/Component

title: Component

$ref: #/definitions/Cargo

$ref: #/definitions/Git

$ref: #/definitions/Go

$ref: #/definitions/Linux

$ref: #/definitions/Maven

$ref: #/definitions/Npm

$ref: #/definitions/NuGet

$ref: #/definitions/Other

$ref: #/definitions/Pip

$ref: #/definitions/Pod

$ref: #/definitions/RubyGems

$ref: #/definitions/VCPKG

title: Cargo

required: name version

required: type cargo

title: Git

required: commitHash repositoryUrl

required: type git

title: Go

required: type go

title: Linux

required: name version distribution release

required: type linux

title: Maven

required: groupId artifactId version

required: type maven

title: Npm

required: type npm

title: NuGet

required: type nuget

title: Other

title: Other

required: name version downloadUrl hash

required: type other

title: Pip

required: type pip

title: Pod

title: RubyGems

title: VCPKG

title: Component Detection manifest