type: array

$ref: #/$defs/ruleset

type: object

type: string

pattern: ^\d+\s(seconds?|minutes?|hours?|days?)$

type: boolean

enum: parallel sequential

default: sequential

$ref: #/$defs/source

$ref: #/$defs/rule

required: hosts sources rules

required: name condition actions

required: name condition action

pattern: \S

$ref: #/$defs/throttle

$ref: #/$defs/all-condition

$ref: #/$defs/any-condition

$ref: #/$defs/not-all-condition

$ref: #/$defs/run-playbook-action

$ref: #/$defs/run-module-action

$ref: #/$defs/run-job-template-action

$ref: #/$defs/run-workflow-template-action

$ref: #/$defs/post-event-action

$ref: #/$defs/set-fact-action

$ref: #/$defs/retract-fact-action

$ref: #/$defs/print-event-action

$ref: #/$defs/debug-action

$ref: #/$defs/none-action

$ref: #/$defs/shutdown-action

type: integer

type: string object

type: number

type: object string


paf-module.schema.json

line_endings: unix

title: Qualisys PAF Module

description: A settings.paf file used by Qualisys Project Automation Framework (PAF) Modules

title: Project ID

description: A human readable name that identifies the project. This name is recorded in data files and should not be changed once data collection has started as doing so will render data files useless.

title: Root type

description: Reference to the class or type name to use at the highest level in the PAF item hierarchy.

title: Date format

description: Specifies what date format to use in this project. Applies mainly to exports and column values but not to the field edit dialog. Accepted values are Iso, Little endian and Middle endian.

enum:
Iso
Little endian
Middle endian

title: Date separator

description: Specifies which token to use to separate the parts of the dates when formatting them. Accepted values are Dash, Slash, Dot and None.

enum: Dash Slash Dot None

title: Time format

description: Specifies what time format to use in this project. Applies mainly to exports and column values but not to the field edit dialog. Accepted values are 12-hour and 24-hour.

title: Filename filter

description: A regular expression that determines which files (in addition to the qtm files) that will be visible in the tree view.

title: Export c3d settings

description: This section is optional and is used when exporting to c3d file.

title: Point units in C3D export

description: Possible units are: mm, cm or m.

enum: mm cm m

title: Default fields

description: A sequence of names of fields that will be added to all types. QTM also adds a number of default fields automatically. For a list of these, see the Default Fields section.

description: This section contains information that the package management system uses. It is used mainly when installing packages and when creating new projects based on a package.

title: Package name

description: The name of the package. Shown when creating a new project and used to keep the connection between a project and the package it was created from to, for instance, know if there is a new version of a package. This means that this value should not be changed unless strictly necessary because that will break the connection between existing projects and new versions of the package.

title: Module version

description: Two numbers separated by a period sign (e.g. 44.23), three numbers separated by period signs (e.g. 1.45.3214), or three numbers separated by a period sign and a build number separated by a plus sign (e.g. 1.3.0+188). The version of the package. Used to keep track of which version a project is based on. Visible in the about box when a project is open. Useful for debugging purposes and for knowing if the package can be upgraded.

title: Required QTM version

description: Two or three digits separated by a period sign. The QTM version that is required for this package to work properly. Checked on install time. Must include major and minor version number and can optionally include build number too.

title: Previous names

description: A sequence of names that this package has had earlier in development. This is used only when checking if a project should be upgraded and allows for packages to be renamed without losing the project upgrade path.

required:
Name
Version
Required QTM version

title: Types definition

title: Type

description: All type names have to be unique. Each class definition is a map that contains the type names as keys and the type definitions as values.

title: Field reference

description: Naming any field as a key and a default value for that field in this type is permitted. Any default value given here overrides the default value from the field specification. The default value should always be a scalar except for string fields that also support sequences. See documentation of the Default property in the Fields section for more information.

title: Class

description: All class names have to be unique. Each class definition is a map that contains the type names as keys and the type definitions as values.

title: Class fields

description: Fields to use for this class. If this key is present it should contain a map or sequence that contains fields that should be defined for each type of this class. If the fields are given as a map they also specify default values for the fields. A type can override the default value of a field by including the field name as part of its own definition but it cannot undefine a field that has been defined in the class.

title: Children types or classes

description: A sequence of references to class or type names that can be created as children to items of this type. A type that has children cannot have measurements.

title: Measurements

description: A sequence of measurement type names. If a type has the measurement property, it is considered to be a session-like type. It cannot have other children and it will have a wizard interface containing measurements (of the types specified by this parameter) and analyses.

title: Analyses

description: A sequence of analysis names. These will be shown in the Analyze dropdown of the session wizard. The first analysis in the list will be the default analysis that is run when the button itself is clicked.

title: Field display order

description: A sequence of field names denoting the order in which to display the fields of items of this type. Inherited fields can also be entered. Fields named here will be displayed first in field lists. Fields that are not named are displayed afterwards in an arbitrary order.

title: Field display order

description: An optional string displayed instead of the type name as a heading for the measurement type in the wizard pane.

title: Path to PDF guide

description: The path to a PDF file to show when the user clicks the Show guide button in the wizard pane.

title: Directory pattern

description:
A naming pattern for the directory created for each item (except measurements, for which this property is useless).

The pattern can contain any text as well as names of items braced by $ signs, so for instance the directory pattern “Patient $ID$” would be expanded to Patient followed by the contents of the ID field of that item. In addition to the field names $ClassName$, $TypeName$, $WorkingDirectory$, $TemplateDirectory$ and $InstanceNumber$ can also be used in the naming patterns.

An item reference can also specify additional formatting options, inspired by those of the printf format strings. The syntax is: $[Opt. pad char][Minimum length]:Field name$ so for instance $08:ID$ would print the id field and pad it with zeros to a width of 8 characters.

The default naming pattern is $TypeName$. If directory names clash when a new directory is created, a counter is appended to the name to make it unique.

title: Path to icon file

description: The path to an icon file (.ico) to show at the side of the item in the tree view. The path is relative to the `Templates` folder.

title: Field reference

title: Measurement definitions

title: Measurement

description: A uniquely named measurement, defining its properties.

title: Class fields

title: Default measurement button count

description: The default number of measurement buttons that kind of measurement in a new session.

title: Minimum measurement count

description: The minimum number of measurements of that kind in a session. The +/- buttons will not allow the count to go below this and if any analysis lists this kind of measurement as a prerequisite, the analysis will not be available until the minimum number of measurements have been performed.

title: Maximum measurement count

description: The maximum number of measurements of that kind in a session.

title: Measurement recording length

description: The default length of this kind of measurement.

title: Pretrigger length

description: The length of the pretrigger buffer. Setting this to zero disables pretrigger. Leaving this option out uses the project setting for pretrigger.

title: Measurement frequency

description: The frequency used for this kind of measurement. If omitted, the frequency is not changed when starting the measurement.

title: AIM models

description: A semicolon separated list (not a YAML sequence) of AIM models that should be applied to measurements of this kind.

title: Display fields dialog after creation

description: If this value is set to true, the fields dialog will be displayed when a measurement has finished to allow the user to edit the fields of the measurement item in the same way that dialog is displayed when other (non-measurement) items are created.

$ref: #/$defs/yaml-boolean

title: Measurement heading

title: Field display order

title: Measurement pattern

description:
A naming pattern for measurements created for each item. The pattern can contain any text as well as names of items braced by $ signs, so for instance the measurement pattern “Patient $ID$” would be expanded to Patient followed by the contents of the ID field of that item. In addition to the field names $ClassName$, $TypeName$, $WorkingDirectory$, $TemplateDirectory$ and $InstanceNumber$ can also be used in the naming patterns.

An item reference can also specify additional formatting options, inspired by those of the printf format strings. The syntax is: $[Opt. pad char][Minimum length]:Field name$ so for instance $08:ID$ would print the id field and pad it with zeros to a width of 8 characters.

The default naming pattern is $TypeName$. If directory names clash when a new directory is created, a counter is appended to the name to make it unique. The file extension .qtm will be added automatically. The default value is $TypeName$ $InstanceNumber$.

title: Field reference

title: Analysis definitions

title: Analysis

description: A uniquely named analysis, defining its properties.

title: Analysis type

description:
Names of the analysis type. Valid values are External program, Visual3D, Report, Compound, HTTPRequest, Instantiate template, Create skeleton, Solve skeleton.

Note: only External program and Compound are available to all users. Other types require the Project Automation Framework developer license which is used for internal Qualisys development and by development partners.

enum:
External program
Visual3D
Report
Compound
HTTPRequest
Instantiate template
Create skeleton
Solve skeleton

title: Measurement and/or analysis prerequisites

description: A sequence of measurement type names and analysis names that has to be completed before this analysis can be run. Measurement types are considered complete for the current session when the user has made at least the number of measurements given by that measurement type’s Minimum count field. Analyses are considered complete when the file denoted by the Output file field exists.

title: Output file

description: The name of a file that is created when this analysis is run. QTM uses this to check if the analysis has been completed. It is also used to issue a warning if this file has been changed since the analysis was last run for the current session. This property can contain patterns.

title: Program display name

description:
External program only: The name to be displayed in the directories tab in project options where the user will have to locate the external executable. NB: Because this path varies between computers rather than between projects, it is not stored in the project, but in computer-global settings file.

Several analyses in different projects may share the same Program display name and QTM will automatically use the same executable path for all of them.

title: Export session

description: External program only: Optional. If present, the metadata of the session, all its ancestors and the measurements are exported into a file called session.xml.

title: Formats for measurement exports

description: External program only: Optional. A single string or an array containing any combination of the following values: “TSV”, “C3D”, “MAT”. Will make QTM export all the selected measurements to the corresponding formats before running the external program. Use “xml settings” to export a file with measurement settings (e.g. capture start time and analog channel names). The file will be named [file name].settings.xml.

enum:
TSV
C3D
MAT
JSON
tsv
c3d
mat
json
xml settings

title: Template files

description: External program only: Optional. A single string or an array containing names of files in the template directory. Each file will be run through the PHP engine and the result written to a file with the same name in the session directory. Standard Windows wildcards are supported, but note that if the asterisk is used to match a part of the filename, the pattern must be enclosed in single quotation marks to make sure it is not parsed as a YAML alias.

title: Working directory

description: External program only: Optional. The working directory set when the program is launched. Defaults to the session directory.

title: Arguments

description: Optional. An array of arguments to be sent to the program being started. Each argument will be subject to pattern expansion and if the result contains spaces, it will be enclosed in double quotation marks when the command line is built.

title: Show output file

description: External program only: Optional. If set, and if the Output file property has been specified, and if the execution of the external program is successful (exit code 0), the output file will be shown in the systems standard program for that file type (as if it was double-clicked in the windows explorer).

title: Do not wait for Application

description: External program only: Optional. If analysis includes this property, QTM does not wait for external program to finish the processing. If property does not exit, to continue with subsequent analyses, external program must be closed manually (> QTM 2019.1).

title: Pipeline template

description: Visual3D analysis only: Required. The name of a template file in the Templates directory. This file will be instantiated and used as the pipeline script in visual 3d.

title: Do not wait for Visual3D

description: Visual3D analysis only: Optional. If analysis includes this property, QTM does not wait for Visual3D to finish the processing. If property does not exit, to continue with subsequent analyses, Visual3D must be closed manually or Exit_Workspace; command has to be added to the very end of Visual3D script.

title: Deprecated: Close Visual3D

description: Visual3D analysis only: Deprecated (> QTM 2.16).

enum:
Never
No Warnings

title: Compound analysis components

description: Compound analysis only. Required. An array of analysis steps.

title: Template to instantiate

description: Instantiate template analysis only: Required. The name of the input file. If this name contains any path delimiter tokens, it will be considered to be relative to the project directory, otherwise QTM will assume that the input file is placed in the templates folder.

title: Measurements where skeleton should be solved

description: Create / Solve skeleton analyses only: Required. A string or list of strings to specify the file names to solve the skeletons. Wildcard can be used in the name to specify multiple files at once. To specify all measurements, simply use the wildcard character. Only measurements that are marked as used in the PAF pane will be affected.

title: Measurements where skeleton should _not_ be solved

description: Create / Solve skeleton analyses only: Optional. A string or list of strings to specify the file names to exclude. Wildcard can be used in the name to specify multiple files at once. Only measurements that are marked as used in the PAF pane will be affected.

title: Field definitions

title: Field

description: A uniquely named field, defining its properties.

title: Field type

description: Required. Defines the type of the field. Possible values are Integer, Float, String, Date, TimeOfDay, Enum or Boolean.

enum: Integer Float String Date TimeOfDay Enum Boolean

title: Hidden field

description: If the value is Yes or True, this field will not be displayed in the GUI (and thus will not be editable by the user) but will be exported to files. It will keep its default value.

title: Readonly field

description: If the value is Yes or True this field will be displayed, but the user will not be able to edit it. It will keep its default value.

title: Inherit from parent fields

description:
This field will be inherited by all subitems of the item that contains it. There are two modes of inheritance Copy and Connect and the value of this property has to be one of them.

Copy: Inheritance by copying means that when a child to an item that has an inheritable field is created, a field with the same name is created in the child and the value of the field in the parent is copied to that field.

Connect fields work the same way when an item is created, but if the field is changed in any of the items (any ancestor or heir) it is updated in all the items that have inherited this field from the same origin. If, for instance, a value is inherited by connection from a patient to a number of sessions and the measurements in those sessions and it is changed in one of the sessions it is changed in all those objects, but not in other patients and the sessions of those patients.

Fields are inherited all the down to the leaves from the item including the fields so if the root item would include an inherited field, it would be copied to all items in the tree.

enum: Copy Connect

title: Default field value

description: The default value that this field will get when an item that contains it is created. This can be overridden in the item type specification and by inheritance. The value of this property should have the same data type as the field. String fields can also specify a sequence as default value. The sequence will be converted into a string containing the elements of the sequence separated by semicolon.

title: Maximum value

description: Integer / Float types only: The maximum value that can be entered in this field.

title: Minimum value

description: Integer / Float types only: The minimum value that can be entered in this field.

title: Field physical quantity

description: Float type only: The physical quantity that this field represents. This list contains the basic physical quantities but also some derived quantities because there is no possibility to combine quantities.

enum:
Length
Mass
Voltage
Current
Force
Moment
Power
Angle
Time
Frequency
Temperature
Speed
Acceleration
Magnetic field strength
Rotational speed

title: Field unit

description: Float type only: The unit of this field. Can only be specified if a quantity has been specified. Different units apply to different quantities. Either the unit name or the abbreviation can be given. If a unit is not entered, the S/I unit is used.

enum:
meters
ångstroms
nanometers
microns
millimeters
centimeters
kilometers
inches
feet
yards
miles
kilograms
micrograms
milligrams
grams
ounces
pounds
volts
nanovolts
microvolts
millivolts
kilovolts
ampere
nanoampere
microampere
milliampere
kiloampere
newtons
millinewtons
kilonewtons
meganewtons
kiloponds
pounds force
newtonmeter
newtonmillimeter
watt
radians
degrees
seconds
minutes
hours
hertz
kilohertz
megahertz
revolutions per minute
beats per minute
kelvin
degrees celsius
degrees farenheit
meters per second
millimeters per second
kilometers per hour
feet per second
miles per hour
knots
meters per second squared
millimeters per second squared
feet per second squared
standard gravity
tesla
millitesla
degrees per second
Meters
Ångstroms
Nanometers
Microns
Millimeters
Centimeters
Kilometers
Inches
Feet
Yards
Miles
Kilograms
Micrograms
Milligrams
Grams
Ounces
Pounds
Volts
Nanovolts
Microvolts
Millivolts
Kilovolts
Ampere
Nanoampere
Microampere
Milliampere
Kiloampere
Newtons
Millinewtons
Kilonewtons
Meganewtons
Kiloponds
Pounds force
Newtonmeter
Newtonmillimeter
Watt
Radians
Degrees
Seconds
Minutes
Hours
Hertz
Kilohertz
Megahertz
Revolutions per minute
Beats per minute
Kelvin
Degrees celsius
Degrees farenheit
Meters per second
Millimeters per second
Kilometers per hour
Feet per second
Miles per hour
Knots
Meters per second squared
Millimeters per second squared
Feet per second squared
Standard gravity
Tesla
Millitesla
Degrees per second
m/s

title: Field decimal count

description: Float type only: The number of decimals to present to the user.

title: Force non-empty string

description: String type only: Force the string to be non-empty.

title: Treat string as JSON object

description: String type only: The string should be returned as JSON object when queried from the REST api. JSON fields are not exported to session.xml during the analysis step. (Available from QTM 2.14).

title: Enum values

description:
Enum type only: The enum field defines an enumeration. To the user it will be presented as a multiple selection and internally it will be saved as a numeric value. The possible values that an enum can have has to be specified in the Values property. This property can be either a sequence or a map.

If it is a sequence it simply lists the choices of the enum and these will be assigned an integer value automatically.

If it is a map it is a map from the choices to the numeric value of each particular choice.

title: Boolean display

description: Boolean type only: Controls how this value will be displayed. Can be one of yesno, checkbox or truefalse.

enum: yesno checkbox truefalse YesNo Checkbox TrueFalse

title: Column definitions

description: The columns section specifies the columns of the tree view in the project view. It allows the PAF file to specify multiple column setups. The idea is that the users should be able to switch between different configurations and possibly also add their own but currently only the first setup is used.

title: Column setup

description: A uniquely named column setup. Each setup contains an arbitrary number of columns.

title: Column

description: A uniquely named column. Each column can specify a width (in pixels) and a way of determining the value displayed in the column. A key to understanding the column values is the understanding that each row in the tree view might contain a different type of item.

title: Column width

description: The width (in pixels) of this column.

title: Column field

description: The column will contain the value of the field named by this property regardless of the type of the item on the row.

title: Column fields (with name mapping)

description: A map from the item type name to the field to use. For each item type that is present as a key in the map the value of the field named will be used. For item types that are not named in the map the default field name will be used.

title: Default field

description: Name used for item types not named in the map.

title: Field mapping

title: Type name

title: Editable values

description: If yes or true, the value of the field can be edited directly in the tree.


ninjs

description: A news item as JSON object -- copyright 2021 IPTC - International Press Telecommunications Council - www.iptc.org - This document is published under the Creative Commons Attribution 4.0 license, see  http://creativecommons.org/licenses/by/4.0/

title: Uniform Resource Identifier

description: The global unique identifier for this news object. This is the only required property and should identify the ninjs object, not be used for links to external resources etc.  nar:newsItem@guid

format: uri

title: Type

description: The generic news type of this news object. (Value 'component' added in version 1.2 as issue #21.). See: http://cv.iptc.org/newscodes/ninature/ nar:itemClass

enum: text audio video picture graphic composite component

title: Representation type

description: Indicates how complete this representation of a news item is. No mapping to nar. Specific for ninjs.

enum: full partial

title: Profile

description: An identifier for the structure of the news object. This can be any string but we suggest something identifying the structure of the content such as 'text-only' or 'text-photo'. Profiles are typically provider-specific. nar:profile

title: Version

description: The version of the news object which is identified by the uri property. nar:newsItem@version

title: First created

description: Indicates when the first version of this ninjs object was created. (Added in version 1.2 from issue #5). nar:firstCreated

format: date-time

title: Version created

description: The date and time when this version of this ninjs object was created. nar:versionCreated

title: Content created

description: The date and time when the content of this ninjs object was originally created. For example and old photo that is now handled as a ninjs object. nar:contentCreated

title: Embargoed

description: The date and time before which all versions of the news object are embargoed. If absent, this object is not embargoed. nar:embargoed

title: Publication status

description: The publishing status of the news object, its value is *usable* by default. nar:pubStatus

enum: usable withheld canceled

title: Urgency

description: The editorial urgency of the content. Values from 1 to 9. 1 represents the highest urgency, 9 the lowest. nar:urgency

title: Copyright holder

description: The person or organisation claiming the intellectual property for the content. nar:copyrightHolder

title: Copyright notice

description: Any necessary copyright notice for claiming the intellectual property for the content. nar:copyrightNotice

title: Usage terms

description: A natural-language statement about the usage terms pertaining to the content. nar:usageTerms

title: Editorial note

description: A note that is intended to be read by internal staff at the receiving organisation, but not intended to be published. (Added in version 1.2 from issue #6.). (Consider using this before using the descriptions array.) ednote: nar:edNote

title: Language

description: The human language used by the content. The value should follow IETF BCP47. nar:language

title: Descriptions

description: An array of one or more descriptions of the ninjs object. See also ednote for information from provider to reciever. Descriptions are seen as metadata. For a simple description use an array with one object only containing the value property. Role and contenttype are then undefined and it is up to the provider.

title: Role

description: The role of this description

title: Content Type

description: The IANA (Internet Assigned Numbers Authority) MIME type of the content of this description.

title: Value

description: The descriptive text identified with the above role (and contenttype).

title: Bodies

description: An array of body objects with the content as text or with markup. For a simple body use an array with one object only containing the value property. Role and contenttype are then undefined and it is up to the provider.

title: Role

description: The role of this body

title: Content Type

description: The IANA (Internet Assigned Numbers Authority) MIME type of the content of this body.

title: Character count

description: The total character count in this body excluding figure captions. (Added in version 1.2 according to issue #27.). nar:charcount

title: Word count

description: The total number of words in this body excluding figure captions. (Added in version 1.2 according to issue #27.). nar:wordcount

title: Value

description: The body text identified with the above role and contenttype.

title: Headlines

description: An array of objects containing various types of headlines. For a simple headline use an array with one object only containing the value property. Role and contenttype are then undefined and it is up to the provider.

title: Role

description: The role of this headline

title: Content Type

description: The IANA (Internet Assigned Numbers Authority) MIME type of the content of this headline.

title: Value

description: The headline identified with the above role and contenttype.

title: People

description: An array of objects describing individual human beings. nar:subject

title: Name

description: The name of a person

title: Relationship

description: The relationship of the content of the news object to the person

title: URI

description: The identifier for the person as a complete uri with the code.

title: Literal

description: The code for the person as a literal value.

title: Organisations

description: An array of objects describing administrative and functional structures which may, for example, act as as a business, as a political party or not-for-profit party. nar:subject

title: Name

description: The name of the organisation

title: Relationship

description: The relationship of the content of the news object to the organisation

title: URI

description: The identifier of the organisation as a complete uri

title: Literal

description: The code for the organisation as a literal

title: Symbols

description: Symbols used for a financial instrument linked to the organisation at a specific market place

title: Ticker

description: Ticker symbol used for the financial instrument

title: Exchange

description: Identifier for the marketplace which uses the ticker symbols of the ticker property

title: Places

description: An array of named locations. nar:subject

title: Name

description: The name of the place

title: Relationship

description: The relationship of the content of the news object to the place

title: URI

description: The identifier for the place as a complete uri

title: Literal

description: The code for the place as a literal

title: Subjects

description: An array of objects holding concepts with a relationship to the content. nar:subject

title: Name

description: The name of the subject

title: Relationship

description: The relationship of the content of the news object to the subject

title: URI

description: The identifier of the subject as a complete uri

title: Literal

description: The code for the subject as a string literal

title: Events

description: An array of objects describing something which happens in a planned or unplanned manner. nar:?

title: Name

description: The name of the event

title: Relationship

description: The relationship of the content of the news object to the event

title: URI

description: The identifier for the event as a complete uri

title: Literal

description: The code for the event as a string literal

title: Objects

description: An array of objects describing something material, excluding persons. nar:subject

title: Name

description: The name of the object

title: Relationship

description: The relationship of the content of the news object to the object

title: URI

description: The identifier for the object as a complete uri

title: Literal

description: The code for the object as a string literal

title: Info sources

description: An array of parties (person or organisation) which originated, modified, enhanced, distributed, aggregated or supplied the content or provided some information used to create or enhance the content. (Added in version 1.2 according to issue #15.) .  infosource:  nar:infoSource

title: Name

description: The name of the infosource

title: Role

description: The role the infosource in relationship to the content as a uri.

title: URI

description: The identifier of the infosource as a complete uri

title: Literal

description: The code for the infosource as a string literal

title: Title

description: A short natural-language name for the item. Title is metadata, use headlines for publishable headlines. (Added in version 1.2 according to issue #9). nar:itemMeta/title

title: By

description: A natural-language statement about the creator (author, photographer etc.) of the content. nar:by

title: Slugline

description: A human-readable identifier for the item. (Added in version 1.2 from issue #4.). nar:slugline

title: Located

description: The name of the location from which the content originates. nar:located

title: Renditions

description: An array of objects with different renditions of the news object. nar:remoteContent

description: A specific rendition of the content of the news object. (Description changed in version 1.2 according to issue #17.)

title: Name

description: The name of this object in the array of renditions. For example 'thumbnail'

title: href

description: The URL for accessing the rendition as a resource. nar:remoteContent@ref

title: Content Type

description: A MIME type which applies to this rendition. nar:remoteContent@contenttype

title: Title

description: A title for the link to the rendition resource

title: Height

description: For still and moving images: the height of the display area measured in pixels. nar:remoteContent@height

title: Width

description: For still and moving images: the width of the display area measured in pixels. nar:remoteContent@width

title: Size in bytes

description: The size of the rendition resource in bytes

title: Duration

description: The total time duration of the content in seconds. (Added in version 1.2. Issue #18). nar:remoteContent@duration

title: Format

description: Binary format name. (Added in version 1.2. Issue #18). nar:remoteContent@format

title: Associations

description: An array of objects with content of news objects which are associated with this news object.

description: One associated object where each object can use all properties in ninjs.

description: The name of this object in the array of associations. For example 'logo'

title: Alternative ids

description: Alternative identifiers assigned to the content. Each alternative id can have a role and a value. nar:altId issue #3.

title: Role

description: The role of the alternative id

title: Value

description: The alternative id value

title: Trust indicators

description: An array of objects to allow links to documents about trust indicators. issue #44. (Added in version 1.3)

title: Role

description: The role of the trust indicator as a complete uri

title: Title

description: The title of the resource being referenced.

title: href

description: The URL for accessing the trust indicator resource.

title: Standard

description: An object with information about standard, version and schema this instance is valid against. nar:standard, nar:standardversion and xml:schema issue #43. (Added in version 1.3)

title: Name of standard.

description: For example ninjs. nar:standard

title: Version of standard.

description: For example 1.3. nar:standardversion

title: Schema

description: The uri of the json schema to use for validation.

title: Genres

description: A nature, intellectual or journalistic form of the content. nar:genre. (Added in version 1.3)

title: Name

description: The name of the genre

title: URI

description: The identifier of  the genre as a complete uri

title: Literal

description: The code for the genre as a string literal

title: Rights information

description: Expression of rights to be applied to content. nar:rightsInfo

title: Language id

description: Identifier for the Rights Expression language used. nar:@langid

title: Linked rights

description: A link from the current Item to Web resource with rights related information. nar:link

title: Encoded Rights

description: Contains a rights expression as defined by a Rights Expression Language. nar:rightsExpressionXML or nar:rightsExpressionData

title: IPTC ninjs - News in JSON - version 2.0 (approved at IPTC Standards Committee October 2021)


snapcraft.json

usage: <string>

usage: on <selector>[,<selector>...]:

$ref: #/definitions/grammar-string

usage: to <selector>[,<selector>...]:

usage: try:

usage: else:

pattern: else fail

$ref: #/definitions/grammar-array

$ref: #/definitions/build-environment-grammar

description: deb repositories

description: Architectures to enable, or restrict to, for this repository.  Defaults to host architecture.

description: deb types to enable.  Defaults to [deb, deb-src].

enum: deb deb-src

description: Deb repository components to enable, e.g. 'main, multiverse, unstable'

description: GPG key identifier / fingerprint. May be used to identify key file in <project>/snap/keys/<key-id>.asc

description: GPG keyserver to use to fetch GPG <key-id>, e.g. 'keyserver.ubuntu.com'. Defaults to keyserver.ubuntu.com if key is not found in project.

description: Exact path to repository (relative to URL). Cannot be used with suites or components.

description: Deb repository suites to enable, e.g. 'xenial-updates, xenial-security').

description: Deb repository URL, e.g. 'http://archive.canonical.com/ubuntu'.

required: type key-id url

validation-failure: {!r} is not properly configured deb repository

description: PPA repository

description: ppa path: e.g. 'canonical-kernel-team/unstable'

required: type ppa

validation-failure: {!r} is not properly configured PPA repository

description: short-form user configuration (<username>: <scope>)

validation-failure: {!r} is not a valid user scope. Valid scopes include: 'shared'

description: environment entries

title: snapcraft schema

description: top level build packages.

description: name of the part that provides source files that will be parsed to extract snap metadata information

description: name of the snap package

$comment: string, but not too long. the failure message avoids printing repr of the thing, as it could be huge

validation-failure: snap names need to be strings.

validation-failure: {.instance!r} is not a valid snap name. Snap names can only use ASCII lowercase letters, numbers, and hyphens, and must have at least one letter.

validation-failure: {.instance!r} is not a valid snap name. Snap names cannot start with a hyphen.

validation-failure: {.instance!r} is not a valid snap name. Snap names cannot end with a hyphen.

validation-failure: {.instance!r} is not a valid snap name. Snap names cannot have two hyphens in a row.

description: title for the snap

description: architectures on which to build, and on which the resulting snap runs

format: architectures

description: package version

validation-failure: snap versions need to be strings. They must also be wrapped in quotes when the value will be interpreted by the YAML parser as a non-string. Examples: '1', '1.2', '1.2.3', git (will be replaced by a git describe based version string).

validation-failure: {.instance!r} is not a valid snap version string. Snap versions consist of upper- and lower-case alphanumeric characters, as well as periods, colons, plus signs, tildes, and hyphens. They cannot begin with a period, colon, plus sign, tilde, or hyphen. They cannot end with a period, colon, or hyphen.

description: a script that echoes the version to set.

description: the license the package holds

description: path to a 512x512 icon representing the package.

format: icon-path

description: one line summary for the package

description: long description of the package

validation-failure: {.instance!r} is not a valid description string.

description: featureset the snap requires in order to work.

description: the snap type, the implicit type is 'app'

enum: app base gadget kernel snapd

description: the type of confinement supported by the snap

default: strict

enum: classic devmode strict

description: the quality grade of the snap

default: stable

description: the base snap to use

description: force a build environment based on base to create a snap

description: the snap epoch, used to specify upgrade paths

description: compression to use for snap archive - default is otherwise determined by 'snap pack'

description: environment entries for the snap as a whole

description: properties to be passed into snap.yaml as-is

description: layout property to be passed into the snap.yaml as-is

description: additional repository configuration.

description: system username

description: long-form user configuration

validation-failure: {!r} is not a valid app name. App names consist of upper- and lower-case alphanumeric characters and hyphens. They cannot start or end with a hyphen.

description: Name of the desktop file placed by the application in $SNAP_USER_DATA/.config/autostart to indicate that application should be started with the user's desktop session.

validation-failure: {.instance!r} is not a valid desktop file name (e.g. myapp.desktop)

description: common identifier across multiple packaging formats

description: D-Bus name this service is reachable as

description: dbus interface slots this service activates on

description: path to a desktop file representing the app, relative to the prime directory

description: command executed to run the binary

description: bash completion script relative to the prime directory

description: command executed to stop a service

description: command executed after stopping a service

validation-failure: {.instance!r} is not a valid timeout value.

description: Optional time to wait for daemon to start - <n>ns | <n>us | <n>ms | <n>s | <n>m

description: Optional time to wait for daemon to stop - <n>ns | <n>us | <n>ms | <n>s | <n>m

description: Service watchdog timeout - <n>ns | <n>us | <n>ms | <n>s | <n>m

description: Command to use to ask the service to reload its configuration.

validation-failure: {.instance!r} is not a valid delay value.

description: Delay between service restarts - <n>ns | <n>us | <n>ms | <n>s | <n>m. Defaults to unset. See the systemd.service manual on RestartSec for details.

description: The service is activated by a timer, app must be a daemon. (systemd.time calendar event string)

description: signals that the app is a service.

description: List of applications that are ordered to be started after the current one

description: List of applications that are ordered to be started before the current one

description: controls if the app should be restarted at all

description: controls how the daemon should be stopped

enum: on-success on-failure on-abnormal on-abort on-watchdog always never

validation-failure: {.instance!r} is not a valid alias. Aliases must be strings, begin with an ASCII alphanumeric character, and can only use ASCII alphanumeric characters and the following special characters: . _ -

description: environment entries for the specific app.

$comment: Full should be the default, but it requires command-chain which isn't available in snapd until 2.36, which isn't yet stable. Until 2.36 is generally available, continue with legacy as the default.

description: What kind of wrapper to generate for the given command

validation-failure: {.instance!r} is not a valid command-chain entry. Command chain entries must be strings, and can only use ASCII alphanumeric characters and the following special characters: / . _ # : $ -

validation-failure: {!r} is not a valid socket name. Socket names consist of lower-case alphanumeric characters and hyphens.

description: Sockets for automatic service activation

usage: port number, an integer between 1 and 65535

validation-failure: {!r} is not a valid hook name. Hook names consist of lower-case alphanumeric characters and hyphens. They cannot start or end with a hyphen.

description: environment entries for this hook

validation-failure: {!r} is not a valid part name. Part names consist of lower-case alphanumeric characters, hyphens and plus signs. As a special case, 'plugins' is also not a valid part name.

description: plugin name

description: submodules to fetch, by pathname in source tree

enum: bzr git hg mercurial subversion svn tar zip deb rpm 7z local

$comment: For some reason 'default' doesn't work if in the ref

enum: core22-step-dependencies enable-patchelf no-patchelf no-install debug keep-execstack

description: UA services to enable.

usage: type: <base|kernel|snapd> (without a base)


schema-org-action.json

description: This is a JSON schema representation of the schema.org Action schema: https://schema.org/Action

format: regex

description: override the @context property to ensure the schema.org URI is used

pattern: Action

description: override the @type property to ensure Action is used

description: Indicates the current disposition of the Action.

description: The direct performer or driver of the action (animate or inanimate). e.g. John wrote a book.

description: Organization

description: Person

description: The endTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to end. For actions that span a period of time, when the action was performed. e.g. John wrote a book from January to December.

description: For failed actions, more information on the cause of the failure.

description: The object that helped the agent perform the action. e.g. John wrote a book with a pen.

description: The location of for example where the event is happening, an organization is located, or where an action takes place.

description: Place

description: PostalAddress

description: The object upon the action is carried out, whose state is kept intact or changed. Also known as the semantic roles patient, affected or undergoer (which change their state) or theme (which doesn't). e.g. John read a book.

description: Other co-agents that participated in the action indirectly. e.g. John wrote a book with Steve.

description: Organization

description: Person

description: Organization

description: Person

description: The result produced in the action. e.g. John wrote a book.

description: The startTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to start. For actions that span a period of time, when the action was performed. e.g. John wrote a book from January to December.

description: Indicates a target EntryPoint for an Action.

title: JSON schema for schema.org / Action


$ref: #/definitions/dependencies

$ref: #/definitions/compilationOptions

default: default

enum: default build

type: string array

description:
A command line script or scripts.

Available variables:
%project:Directory% - The project directory
%project:Name% - The project name
%project:Version% - The project version

description: List of files to exclude from publish output (kpm bundle).

description: Glob pattern to specify all the code files that needs to be compiled. (data type: string or array with glob pattern(s)). Example: [ "Folder1\*.cs", "Folder2\*.cs" ]

description: Configurations are named groups of compilation settings. There are 2 defaults built into the runtime namely 'Debug' and 'Release'.

description: The description of the application

description: Glob pattern to indicate all the code files to be excluded from compilation. (data type: string or array with glob pattern(s)).

$ref: #/definitions/configType

description: Glob pattern to indicate all the code files to be preprocessed. (data type: string with glob pattern).

description: Glob pattern to indicate all the files that need to be compiled as resources.

description: Scripts to execute during the various stages.

$ref: #/definitions/script

description: Glob pattern to specify the code files to share with dependent projects. Example: [ "Folder1\*.cs", "Folder2\*.cs" ]

description: The version of the application. Example: 1.2.0.0

description: Specifying the webroot property in the project.json file specifies the web server root (aka public folder). In visual studio, this folder will be used to root IIS. Static files should be put in here.

title: JSON schema for ASP.NET project.json files


description: Internet email address conforming to most of RFC 822 syntax rules and by that allowing a majority of internalized email addresses as well.

$ref: #/definitions/ConfigParamKey

enum: viewScan exportData administerGe administerProjects administerCache publishScan testDistribution readCache writeCache accessAllProjects accessAnonymousProjectData

required: systemPassword version

description: Gradle Enterprise configuration schema

description: The version of the config file model (must be 7).

description: The amount of heap memory allocated to the application

description: The amount of off-heap memory allocated to the application

description: Configuration parameters for the application

description: The amount of memory for the scan payload event stream cache

description: Permissions to assign to anonymous users - does not support administerGe, administerCache, or testDistribution

enum: ldap saml

const: ldap

required: connectionUrl displayName roles users

description: Distinguished name for the LDAP user account

$ref: #/definitions/EncryptedSecret

description: Password for the LDAP user account

required: dn password

description: Binding information used when LDAP requires authentication

description: URL used to connect to LDAP server

description: Name of this identity provider configuration

const: external

required: baseDn membershipAttribute membershipAttributeType nameAttribute objectClass

description: Base DN for the subtree holding roles

description: Name of the LDAP attribute holding role membership

enum: dn uid

description: Type of the membership-ldap-attribute

description: Name of the LDAP attribute holding the role name

description: LDAP object classes for roles

description: Type of roles retrieve strategy (defaults to GROUP_MEMBER)

const: local

enum: external local

description: Holds information when the identity provider manages roles

description: Name of the LDAP attribute holding email address

description: Name of the LDAP attribute holding first name

description: Name of the LDAP attribute holding last name

description: Name of the LDAP attribute holding user name

description: Name of the LDAP attribute holding a unique id

required: email firstName lastName userName uuid

description: Describes how user attributes are mapped

description: Base DN for the subtree holding users

description: LDAP search filter expression.

description: Optional LDAP filter expression to limit access

required: attributes baseDn

const: saml

required: displayName idpMetadata roles

description: SAML metadata that describes this identity provider

description: Encrypt SAML assertions?

description: Sign authentication requests?

description: Enable signature validation of SAML assertions?

description: Enable signature validation of SAML responses?

description: Groups all options and is only necessary when one or more needs to be enabled

description: Name of the SAML attribute holding role names

description: Name of the SAML attribute holding email address

description: Name of the SAML attribute holding first name

description: Name of the SAML attribute holding last name

$ref: #/definitions/Role

description: Whether to allow access to the SCIM API for user and group management

$ref: #/definitions/HashedSecret

description: The hash of the token

description: The length of the token

description: The prefix of the token

required: hash length prefix

description: Token to authenticate with the SCIM API

description: Configuration for System for Cross-domain Identity Management (SCIM) support

description: The maximum time before an access token is expired (in minutes), default is 10 minutes

description: The time a login session is allowed to be idle before it expires (in minutes), default is 4 days (5760 minutes)

description: The maximum time before a login session is expired (in minutes), default is 30 days (43200 minutes)

description: Timeouts you can specify for user logins in Gradle Enterprise

description: Configuration of Gradle Enterprise authentication options

description: How many old backups to keep

description: Send an email when backup is complete

description: Time (in UTC) to perform the backup

enum: monday tuesday wednesday thursday friday saturday sunday

description: Day (in UTC) to perform the backup

description: Time (in UTC) to perform the backup

description: Custom cron expression for backup time

description: Automatic backup configuration

description: Allow communication with nodes running over untrusted SSL

description: Configuration specific to the build cache app

description: Threshold of free disk space before old scans will be automatically deleted

description: Threshold of free disk space before new scans will be rejected

description: Threshold of free disk space before a warning is sent to users publishing a build scan

description: Storage type of incoming builds

description: How many days of scans should be retained

description: Configuration specific to the build scans app

description: Which time (UTC) should retention-cleanup be performed

description: Email address notifications are sent to

description: SMTP authentication method

description: Email address notifications are sent from

description: Address and port of the smtp server

description: SMTP protocol flavour

description: SMTP configuration for notifications

description: The email address users should contact

description: The name of the contact

description: Who users should contact if they have a problem

description: Required if Gradle Enterprise must communicate with servers using certificates not trusted by default

description: Proxy password

description: Proxy username

description: Proxy authentication credentials

description: A list of hosts that should not be proxied

description: Proxy host

description: Proxy port

description: Proxy protocol

description: Http proxy config

description: Network configuration

description: The name of the bucket to store the scan payloads

description: The aws credentials

description: The region of the bucket

description: Object Storage configuration

description: The password for the system user


sil-kit-registry-configuration.json

description: Configures the properties of the SIL Kit Logging Service

enum: Critical Error Warn Info Debug Trace Off

enum: File Stdout

default: Info

description: Log name; Results in the following filename: <LogName>_%y-%m-%dT%h-%m-%s.txt

description: JSON schema for SIL KIT Registry configuration files.

description: The schema file

description: Version of the schema used to validate this document

description: Free text field allowing a user to describe the configuration file in their own words. The contents of this field are not parsed or used internally.

description: The configured registry instance will listen on this address for incoming connections. Optional; This field overrides the -u, and --listen-uri command line parameters.

$ref: #/definitions/Logging


config.schema.json

$ref: #/definitions/Config

description: List of bazel targets to build

description: List of bazel targets to test

description: Build flags to use in addition to defined in /etc/bazel.bazelrc

description: Test flags to use in addition to defined in /etc/bazel.bazelrc

description: List of branch name masks (doubleglob) to match

description: List of path masks (doubleglob) to match. If not specified, all paths are matched

description: List of branch name masks (doubleglob) to ignore

description: List of path masks (doubleglob) to match. If not specified, all paths are ignored

description: List of tag masks (doubleglob) to match

description: List of tag masks (doubleglob) to ignore

$ref: #/definitions/Workflow

description: The list of FasterCI workflows

$ref: #/definitions/BranchesOrTags

description: Run the workflow on code push

$ref: #/definitions/BranchesAndPaths

description: Run the workflow on pull request

description: Step name, optional

description: Directory to run the step instead of default repo directory

description: Report the result of the step as a separate github check

description: After completing the step, report as a separate Github Check, using the content of the file as a report body, optional

description: Arbitrary command execution; Could be multiline

$ref: #/definitions/BazelStep

description: Bazel step

required: name on

description: Workflow name

$ref: #/definitions/On

description: Event to activate the workflow on

description: Docker image to run the workflow

description: optional cleanup command, executed after the workflow

description: optional maximum number of parallel runs of this workflow

description: Environment variables

description: List of secrets to mount as environment variables

description: Do not notify github

description: Optional command to run before the workflow. Use multiline for multiple commands

$ref: #/definitions/Step

description: List of workflow steps to execute


avro-avsc.json

title: Avro Schema

description: Root Schema

$ref: #/definitions/types

title: Avro Types

description: Allowed Avro types

$ref: #/definitions/primitiveType

$ref: #/definitions/primitiveTypeWithMetadata

$ref: #/definitions/customTypeReference

$ref: #/definitions/avroRecord

$ref: #/definitions/avroEnum

$ref: #/definitions/avroArray

$ref: #/definitions/avroMap

$ref: #/definitions/avroFixed

$ref: #/definitions/avroUnion

title: Primitive Type

description: Basic type primitives.

enum: null boolean int long float double bytes string

title: Primitive Type With Metadata

description: A primitive type with metadata attached.

title: Custom Type

description: Reference to a ComplexType

title: Union

description: A Union of types

$ref: #/definitions/avroSchema

title: Field

description: A field within a Record

$ref: #/definitions/name

enum: ascending descending ignore

required: name type

title: Record

description: A Record

$ref: #/definitions/namespace

$ref: #/definitions/avroField

required: type name fields

title: Enum

description: An enumeration

required: type name symbols

title: Array

description: An array

required: type items

title: Map

description: A map of values

required: type values

title: Fixed

description: A fixed sized array of bytes

required: type name size

description: Json-Schema definition for Avro AVSC files.

title: Avro Schema Definition


chrome-manifest.json

description: Tooltip for the main toolbar icon.

$ref: #/definitions/uri

description: The popup appears when the user clicks the icon.

description: FIXME: String form is deprecated.

description: Icon for the main toolbar.

$ref: #/definitions/icon

description: Tooltip for the main toolbar icon.

$comment: Global shortcuts change the acceptable pattern for the suggested_key.

description: Whether this command should work while Chrome does not have focus. Keyboard shortcut suggestions for global commands are limited to Ctrl+Shift+[0..9]

description: This introduces some fairly strict policies that will make extensions more secure by default, and provides you with the ability to create and enforce rules governing the types of content that can be loaded and executed by your extensions and applications.

format: content-security-policy

default: script-src 'self'; object-src 'self'

format: glob-pattern

format: match-pattern

format: mime-type

format: permission

description: An array of resources to be exposed. Resources are specified as strings and may contain * for wildcard matches. For example, "/images/*" exposes everything in the extension's /images directory recursively while "*.png" exposes all PNG files.

description: A list of URL match patterns specifying which pages can access the resources. Only the origin is used to match URLs; subdomains patterns (*.google.com) and paths are ignored.

description: A list of extension IDs, specifying which extensions can access the resources.

description: If true, only allow resources to be accessible through dynamic ID. The dynamic ID is generated per session. It's regenerated on browser restart or extension reload.

description: The background page is an HTML page that runs in the extension process. It exists for the lifetime of your extension, and only one instance of it at a time is active.

description: When false, makes the background page an event page (loaded only when needed).

$ref: #/definitions/page

description: Specify the HTML of the background page.

$ref: #/definitions/scripts

description: A background page will be generated by the extension system that includes each of the files listed in the scripts property.

description: Use browser actions to put icons in the main Google Chrome toolbar, to the right of the address bar. In addition to its icon, a browser action can also have a tooltip, a badge, and a popup.

description: Use the chrome.pageAction API to put icons inside the address bar. Page actions represent actions that can be taken on the current page, but that aren't applicable to all pages.

description: An array of strings specifying the paths (relative to the package root) of packaged resources that are expected to be usable in the context of a web page.

description: One integer specifying the version of the manifest file format your package requires.

description: The name of the extension

description: One to four dot-separated integers identifying the version of this extension.

description: Specifies the subdirectory of _locales that contains the default strings for this extension.

default: en

description: A plain text description of the extension

description: One or more icons that represent the extension, app, or theme. Recommended format: PNG; also BMP, GIF, ICO, JPEG.

description: Used as the favicon for an extension's pages and infobar.

description: Used on the extension management page (chrome://extensions).

description: Used during installation and in the Chrome Web Store.

description: Override pages are a way to substitute an HTML file from your extension for a page that Google Chrome normally provides.

description: The page that appears when the user chooses the Bookmark Manager menu item from the Chrome menu or, on Mac, the Bookmark Manager item from the Bookmarks menu. You can also get to this page by entering the URL chrome://bookmarks.

description: The page that appears when the user chooses the History menu item from the Chrome menu or, on Mac, the Show Full History item from the History menu. You can also get to this page by entering the URL chrome://history.

description: The page that appears when the user creates a new tab or window. You can also get to this page by entering the URL chrome://newtab.

description: Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension.

$ref: #/definitions/command

description: Content scripts are JavaScript files that run in the context of web pages.

description: Specifies which pages this content script will be injected into.

description: Excludes pages that this content script would otherwise be injected into.

description: The list of CSS files to be injected into matching pages. These are injected in the order they appear in this array, before any DOM is constructed or displayed for the page.

description: The list of JavaScript files to be injected into matching pages. These are injected in the order they appear in this array.

description: The JavaScript world for a script to execute within.

enum: ISOLATED MAIN

default: ISOLATED

description: Controls when the files in js are injected.

description: Controls whether the content script runs in all frames of the matching page, or only the top frame.

description: Applied after matches to include only those URLs that also match this glob. Intended to emulate the @include Greasemonkey keyword.

description: Applied after matches to exclude URLs that match this glob. Intended to emulate the @exclude Greasemonkey keyword.

description: Whether to insert the content script on about:blank and about:srcdoc.

description: A DevTools extension adds functionality to the Chrome DevTools. It can add new UI panels and sidebars, interact with the inspected page, get information about network requests, and more.

description: Declares which extensions, apps, and web pages can connect to your extension via runtime.connect and runtime.sendMessage.

description: The IDs of extensions or apps that are allowed to connect. If left empty or unspecified, no extensions or apps can connect.

description: The URL patterns for web pages that are allowed to connect. This does not affect content scripts. If left empty or unspecified, no web pages can connect.

description: Indicates that the extension would like to make use of the TLS channel ID of the web page connecting to it. The web page must also opt to send the TLS channel ID to the extension via setting includeTlsChannelId to true in runtime.connect's connectInfo or runtime.sendMessage's options.

description: You can use this API to enable users to upload files to your website.

description: Used by event handling code to differentiate between multiple file handlers

description: What the button will display.

description: Filetypes to match.

description: The URL of the homepage for this extension.

description: Specify how this extension will behave if allowed to run in incognito mode.

description: Allows your extension to handle keystrokes, set the composition, and manage the candidate window.

required: name type id description language layouts

description: This value can be used to control the unique ID of an extension, app, or theme when it is loaded during development.

description: The version of Chrome that your extension, app, or theme requires, if any.

description: One or more mappings from MIME types to the Native Client module that handles each type.

description: The location of a Native Client manifest (a .nmf file) within the extension directory.

description: The MIME type for which the Native Client module will be registered as content handler.

description: Use the Chrome Identity API to authenticate users: the getAuthToken for users logged into their Google Account and the launchWebAuthFlow for users logged into a non-Google account.

description: You need to register your app in the Google APIs Console to get the client ID.

description: Whether the app or extension is expected to work offline. When Chrome detects that it is offline, apps with this field set to true will be highlighted on the New Tab page.

description: The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox.

description: The keyword that will trigger your extension.

description: Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary.

description: To allow users to customize the behavior of your extension, you may wish to provide an options page. If you do, a link to it will be provided from the extensions management page at chrome://extensions. Clicking the Options link opens a new tab pointing at your options page.

description: To allow users to customize the behavior of your extension, you may wish to provide an options page. If you do, an Options link will be shown on the extensions management page at chrome://extensions which opens a dialogue containing your options page.

description: The path to your options page, relative to your extension's root.

description: If true, a Chrome user agent stylesheet will be applied to your options page. The default value is false, but we recommend you enable it for a consistent UI with Chrome.

description: If true, your extension's options page will be opened in a new tab rather than embedded in chrome://extensions. The default is false, and we recommend that you don't change it. This is only useful to delay the inevitable deprecation of the old options UI! It will be removed soon, so try not to use it. It will break.

description: Permissions help to limit damage if your extension or app is compromised by malware. Some permissions are also displayed to users before installation, as detailed in Permission Warnings.

description: Technologies required by the app or extension. Hosting sites such as the Chrome Web Store may use this list to dissuade users from installing apps or extensions that will not work on their computer.

description: The '3D' requirement denotes GPU hardware acceleration.

description: List of the 3D-related features your app requires.

description: Indicates if an app or extension requires NPAPI to run. This requirement is enabled by default when the manifest includes the 'plugins' field.

description: Defines an collection of app or extension pages that are to be served in a sandboxed unique origin, and optionally a Content Security Policy to use with them.

description: The short name is typically used where there is insufficient space to display the full name.

description: If you publish using the Chrome Developer Dashboard, ignore this field. If you host your own extension or app: URL to an update manifest XML file.

description: Register itself as a speech engine.

description: Voices the extension can synthesize.

description: Identifies the name of the voice and the engine used.

description: Almost always, a voice can synthesize speech in just a single language. When an engine supports more than one language, it can easily register a separate voice for each language.

description: If your voice corresponds to a male or female voice, you can use this parameter to help clients choose the most appropriate voice for their application.

description: Events sent to update the client on the progress of speech synthesis.

description: In addition to the version field, which is used for update purposes, version_name can be set to a descriptive version string and will be used for display purposes if present.

description: The service worker js file.

description: Used to control the toolbar button for your extension in Chrome's UI.

description: This policy covers pages in your extension, including html files and service workers.

description: This policy covers any sandboxed extension pages that your extension uses.

description: An array of objects that declare resource access rules. Each object maps an array of extension resources to an array of URLs and/or extension IDs that can access those resources.

$comment: browser_action and page_action are no longer present in v3

title: JSON schema for Google Chrome extension manifest files


metadata.json

title: F-Droid Data metadata

description: For every app on F-Droid a metadata file in the format of <application-id>.yml have to be provided, in order to build an app or check or if it has been updated. See https://f-droid.org/docs/Build_Metadata_Reference for a complete reference of a metadata file.

description: Any number of anti-features the application has.

description: Any number of categories for the application to be placed in.

enum:
Connectivity
Development
Games
Graphics
Internet
Money
Multimedia
Navigation
Phone & SMS
Reading
Science & Education
Security
Sports & Health
System
Theming
Time
Writing

description: The name of the author, either full, abbreviated or pseudonym.

description: The e-mail address of the author(s).

description: The website url of the author(s).

$ref: #/definitions/url

description: The URL for the application's web site.

description: The URL to view or obtain the application's source code. This should be something human-friendly.

description: The URL for the application's issue tracker.

description: The URL for the application's translation portal or at least a guide.

description: The URL for the application's changelog.

description: The URL to donate to the project.

description: The project's Flattr (https://flattr.com) ID.

description: The project's Liberapay (https://liberapay.com) user or group name.

description: The project's OpenCollective (https://opencollective.com) user or group name.

description: A Bitcoin address for donating to the project.

description: A Litecoin address for donating to the project.

description: The title of the application, with optional descriptive phrase.

description: The name of the application as can best be retrieved from the source code.

description: DEPRECATED. A brief summary of what the application is. Should rather be provided via Fastlane.

description: DEPRECATED. A full description of the application, relevant to the latest version. Should rather be provided via Fastlane.

description: The lowercase hex value of the SHA-256 fingerprint of the signing certificate of an app. If an APK of that app is not signed by one of these keys, it will not be included in the repository.

description: This is a multi-line field using the same rules and syntax as the description. It's used to record notes for F-Droid maintainers to assist in maintaining and updating the application in the repository.

description: The type of repository - for automatic building from source.

enum: git svn git-svn hg bzr srclib

description: The repository location. Usually a git: or svn: URL, for example.

description: The location of binaries used in verification process.

description: Any number of sub-entries can be present, each specifying a version to automatically build from source.

description: Specifies to build version xxx, which has a version code of yyy.

description: The commit parameter specifies the tag, commit or revision number from which to build it in the source repository.

description: Disables this build, giving a reason why.

description: Specifies to build from a subdirectory of the checked out source code. Normally this directory is changed to before building.

description: Use if the project (git only) has submodules - causes git submodule update --init --recursive to be executed after the source is cloned.

description: Specifies a script to be run using sudo bash -x -c "xxxx" in the Buildserver VM guest. This script is run with full root privileges, but the state will be reset after each build.

description: Time limit for this build (in seconds). After time is up, Buildserver VM is forcefully terminated. The default is 7200 (2 hours); 0 means no limit.

description: Like 'prebuild', but runs on the source code BEFORE any other processing takes place.

description: The sdk location in the repo is in an old format, or the build.xml is expecting such. The 'new' format is sdk.dir while the VERY OLD format is sdk-location.

description: Specifies a particular SDK target for compilation, overriding the value defined in the code by upstream. This has different effects depending on what build system used — this flag currently affects Ant, Maven and Gradle projects only.

description: By default, 'android update' is used in Ant builds to generate or update the project and all its referenced projects. Specifying update=no bypasses that. Note that this is useless in builds that don't use Ant.

const: auto

description: Adds a java.encoding property to local.properties with the given value. Generally the value will be 'utf-8'.

description: If specified, the package version in AndroidManifest.xml is replaced with the version name for the build as specified in the metadata.

description: If specified, the package version code in the AndroidManifest.xml is replaced with the version code for the build. See also forceversion.

description: Specifies the relative paths of files or directories to delete before the build is done.

description: List of external libraries (jar files) from the build/extlib library, which will be placed in the libs directory of the project.

description: Comma-separated list of source libraries or Android projects. Each item is of the form name@rev where name is the predefined source library name and rev is the revision or tag to use in the respective source control.

description: Apply patch(es). 'x' names one (or more - comma-separated) files within a directory below the metadata, with the same name as the metadata file but without the extension. Each of these patches is applied to the code in turn.

description: Specifies a shell command (or commands - chain with &&) to run before the build takes place.

description: Enables one or more files/paths to be excluded from the scan process. This should only be used where there is a very good reason, and probably accompanied by a comment explaining why it is necessary.

description: When running the scan process, any files that trigger errors - like binaries - will be removed. It acts just like scanignore, but instead of ignoring the files, it removes them.

description: As for 'prebuild', but runs during the actual build phase (but before the main Ant/Maven build). Use this only for actions that do actual building. Any preparation of the source code should be done using 'init' or 'prebuild'.

description: Specifies a single or a list of shell commands to run after the build takes place.

description: Enables building of native code via the ndk-build script before doing the main Ant build.

enum: yes no

description: Version of the NDK to use in this build.

description: Build with Gradle instead of Ant, specifying what flavours to use. Flavours are case sensitive since the path to the output APK is as well.

const: yes

description: Build with Maven instead of Ant. An extra @<dir> tells F-Droid to run Maven inside that relative subdirectory.

description: List of Gradle tasks to be run before the assemble task in a Gradle project build.

description: List of Gradle properties to pass via the command line to Gradle. A property can be of the form foo or of the form key=value.

description: Specify an alternate set of Ant commands (target) instead of the default 'release'. It can't be given any flags, such as the path to a build.xml.

description: Specify a glob path where the resulting unsigned release APK from the build should be.

description: Don't check that the version name and code in the resulting APK are correct by looking at the build output - assume the metadata is correct.

description: List of Anti-Features for this specific build. They are described in AntiFeatures.

required: versionName versionCode

description: If this field is present, the application does not get put into the public index. The value should be a description of why the application is disabled.

description: Whether the application requires root privileges to be usable.

description: This determines the number of versions to keep. The older versions of the app are moved to the archive repo, if one is configured. Defaults to 3.

description: This determines the method used for auto-generating new builds when new releases are available - in other words, adding a new Build Version line to the metadata.

description: This determines the method using for determining when new releases are available - in other words, the updating of the CurrentVersion and CurrentVersionCode fields in the metadata by the fdroid checkupdates process.

enum: None Static HTTP

description: A list of operations to be applied to the vercode obtained by the defined UpdateCheckMode. %c will be replaced by the actual vercode, and each string will be passed to python's eval function to calculate a version code.

description: When checking for updates (via UpdateCheckMode) this can be used to specify a regex which, if matched against the version name, causes that version to be ignored.

description: When checking for updates (via UpdateCheckMode) this can be used to specify the package name to search for. Useful when apps have a static package name but change it programmatically in some app flavors, by e.g. appending “.open” or “.free” at the end of the package name.

description: Used in conjunction with UpdateCheckMode for certain modes.

description: The name of the version that is the recommended release. There may be newer versions of the application than this (e.g. unstable versions), and there will almost certainly be older ones.

description: The version code corresponding to the CurrentVersion field.

description: In case we are missing the source code for the CurrentVersion reported by Upstream, or that Non-Free elements have been introduced, this defines the first version that began to miss source code.

required: Categories License Builds

required: Repo RepoType SourceCode

const: 0 versions

pattern: ^Tags

$id: #antifeatures

enum: Ads ApplicationDebuggable KnownVuln NonFreeAdd NonFreeAssets NonFreeDep NonFreeNet NoSourceSince NSFW UpstreamNonFree TetheredNet Tracking


feed.json

description: Use the "authors" key instead, even when there is only one author. Existing feeds can include both "author" and "authors" for compatibility with existing feed readers. Feed readers should always prefer `authors` if present.

description: Is unique for that item for that feed over time. If an item is ever updated, the id should be unchanged. New items should never use a previously-used id. Ideally, the id is the full URL of the resource described by the item, since URLs make great unique identifiers.

description: The language for this item, using the same format as the top-level "language" field. The value can be different than the primary language for the feed when a specific item is written in a different language than other items in the feed.

$ref: #/definitions/item

description: The primary language for the feed in the format specified in RFC 5646. The value is usually a 2-letter language tag from ISO 639-1, optionally followed by a region tag. (Examples: "en" or "en-US".)

description: The URL of the version of the format the feed uses. This should appear at the very top, though we recognize that not all JSON generators allow for ordering.

required: items title version

title: JSON schema for the JSON Feed format


grunt-copy-task.json

$ref: #/definitions/options

description: Set the options for grunt-contrib-copy

description: This option is passed to grunt.file.copy as an advanced way to control which file contents are processed.

description: The file encoding to copy files with.

description: Whether to copy or set the existing file permissions. Set to true to copy the existing file permissions. Or set to the mode, i.e.: 0644, that copied files will be set to.

type: boolean number

title: JSON schema for the Grunt clean task


foundryvtt-system-manifest.json

description: A stable URL that describes the latest release version of your manifest file. This URL is used for automatic system installation in the Foundry VTT setup screen. This manifest URL is consulted during the system update check to see whether a new version is available for download. It is important that this address remain stable, otherwise updates will not be detected.

description: Specifies the default initiative formula if applicable to the system.

description: Integer specifying the default size of a grid space.

description: A label that specifies the default unit of measure used by the system.

examples: ft m

description: An attribute path within the system data model that points to an object that contains both a `value` and a `max` key. The prototype Token will automatically set its primary attribute to this value.

description: An attribute path within the system data model that points to an object that contains both a `value` and a `max` key. The prototype Token will automatically set its secondary attribute to this value.

title: JSON schema for Foundry VTT system files - system.json.


fly.json

description: The path inside your container where the assets to serve are located.

description: The URL prefix that should serve the static assets.

description:
Configure the mapping of ports from the public Fly proxy to your application.

You can have:
* **No services section**: The application has no mappings to the external internet - typically apps like databases or background job workers that talk over 6PN private networking to other apps.
* **One services section**: One internal port mapped to one external port on the internet.
* **Multiple services sections**: Map multiple internal ports to multiple external ports.

description:
Health checks that run as one-off commands directly on the VM.

This type of check is **deprecated**. See `tcp_checks` or `http_checks` for alternatives.

description: The protocol used to communicate with your application. Can be: `tcp` or `udp`.

enum: tcp udp

description: The port this application listens on to communicate with clients. The default is 8080. We recommend applications use the default.

description: Control autoscaling metrics (connections or requests) and limits (hard and soft).

default: connections

enumValues: Autoscale based on number of concurrent connections

enumValues: Autoscale based on number of concurrent requests

enum: connections requests

description: When an application instance is __at__ or __over__ this number, the system will bring up another instance.

description: When an application instance is __at__ or __over__ this number, the system is likely to bring up another instance.

description: For each external port you want to accept connections on, add a `ports` section.

description:
An array of strings that select handlers to terminate the connection at the edge.

Valid options: http, tls, proxy_proto, pg_tls, edge_http.

description: The port to accept traffic on. Valid ports: 1-65535

description: Force HTTP connections to HTTPS. `force_https` requires the `http` handler in the `handlers` section.

description: Basic TCP connection health checks. This is the default check that runs against the configured `internal_port`.

description: The time to wait after a VM starts before checking its health. Units are milliseconds unless you specify them like `10s` or `1m`.

description: Length of the pause between connectivity checks. Units are milliseconds unless you specify them like `10s` or `1m`.

description: The number of consecutive TCP check failures to allow before attempting to restart the VM. The default is `0`, which disables restarts based on failed TCP health checks.

description: The maximum time a connection can take before being reported as failing its healthcheck. Units are milliseconds unless you specify them like `10s` or `1m`.

description: HTTP-based health checks run against the `internal_port`. These checks will pass when receiving a 2xx response. Any other response is considered a failure.

description: The number of consecutive check failures to allow before attempting to restart the VM. The default is `0`, which disables restarts based on failed health checks.

description: The HTTP method to be used for the check.

description: The path of the URL to be requested.

description: The protocol to be used (`http` or `https`)

enum: http https

description: When set to `true` (and `protocol` is set to `https`), skip verifying the certificates sent by the server.

description: Set key/value pairs of HTTP headers to pass along with the check request.

description: Fly.io application name

description: Seconds to wait before forcing a VM process to exit. Default is 5 seconds.

description: Signal to send to a process to shut it down gracefully. Default is SIGINT.

enum: SIGINT SIGTERM SIGQUIT SIGUSR1 SIGUSR2 SIGKILL SIGSTOP

description: The `statics` sections expose static assets built into your application's container to Fly's Anycast network. You can serve HTML files, Javascript, and images without needing to run a web server inside your container.

$ref: #/definitions/statics

$ref: #/definitions/services

description:
Command to run after a build, with access to the production environment, but before deployment. Non-zero exit status will abort the deployment.

```toml
[deploy]
  release_command ="bundle exec rails db:migrate"
```

description: Strategy for replacing VMs during a deployment.

default: canary

enum: canary rolling bluegreen immediate

enumValues: This default strategy - for apps without volumes - will boot a single, new VM with the new release, verify its health, then proceed with a rolling restart strategy.

enumValues: One by one, each running VM is taken down and replaced by a new release VM. This is the default strategy for apps with volumes.

enumValues: For every running VM, a new one is booted alongside it. All new VMs must pass health checks to complete deployment, when traffic gets migrated to new VMs. If your app has multiple VMs, this strategy may reduce deploy time and downtime, assuming your app is scaled to 2 or more VMs.

enumValues: Replace all VMs with new releases immediately without waiting for health checks to pass. This is useful in emergency situations where you're confident a release will be healthy.

defaultValue: Default is 'canary': boot a single, new VM with the new release, verify its health, then proceed with a rolling restart strategy.

description:
Mount [persistent storage volumes](https://fly.io/docs/reference/volumes) previously setup via `flyctl`. Both settings are required. Example:

```toml
[mounts]
  source = "myapp_data"
  destination = "/data"
```

required: source destination

description:
The name of the volume to mount as shown in `fly volumes list`.

A volume of this name *must exist* in each of the app regions. If there's more than one volume in the target region with the same one, one will be picked randomly.

description: The path at which the `source` volume should be mounted in the running app VM.

description: The name of the process(es) to which this mount should be applied. See [multiple processes](https://community.fly.io/t/preview-multi-process-apps-get-your-workers-here/2316).

description: Flags and features that are subject to change, deprecation or promotion to the main configuration.

description:
Override the server command (CMD) set by the Dockerfile. Specify as an array of strings:

```toml
cmd = ["path/to/command", "arg1", "arg2"]
```

description:
Override the ENTRYPOINT set by the Dockerfile. Specify as an array of strings:

```toml
entrypoint = ["path/to/command", "arg1", "arg2"]
```

description: Failed deployments should roll back automatically to the previous successfully deployed release. Defaults to `true`

description: Enables private network access to the Fly organization. Defaults to `true`.

description:
Set non-sensitive information as environment variables in the application's [runtime environment](https://fly.io/docs/reference/runtime-environment/).
For sensitive information, such as credentials or passwords, use the [secrets command](https://fly.io/docs/reference/secrets). For anything else though, the `env` section provides a simple way to set environment variables. Here's an example:
```toml
[env]
  LOG_LEVEL = "debug"
  S3_BUCKET = "my-bucket"
```

description: Build configuration options. See docs at https://fly.io/docs/reference/builders.

description: Builder Docker image to be used with the 'buildpacks' option

description: Buildpacks to be run by the 'builder' Docker image

description:
Build arguments passed to both Dockerfile and Buildpack builds. These arguments are **not available** on VMs at runtime.
```toml
[build.args]
  USER = "julieta"
  MODE = "production"
```

description: Specify the target stage for [multistage Dockerfile builds](https://docs.docker.com/develop/develop-images/multistage-build/).

description: Docker image to be deployed (skips the build process)

description: Dockerfile used for builds. Defaults to './Dockerfile'

title: Fly.io config schema (fly.toml)


clib.json

description:
The name of the package

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#name

description:
The semantic version number of the package. This number should also be a git tag.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#version

description:
An array of source files that make up the implementation of your package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#src

description:
A dictionary of packages and their versions. Each entry represents a package dependency. A dependency must be a clib package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#dependencies

description:
Development dependencies are for testing and development purposes.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#development

description:
he GitHub slug for your package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#repo

description:
A short-and-sweet description of your package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#description

description:
An array of keywords which describe your package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#keywords

description:
The license your package is released under.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#license

description:
Your package's Makefile.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#makefile

description:
Define a script to install your package. This is for executables and libraries only.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#install

description:
Define a script to uninstall your package.

https://github.com/clibs/clib/wiki/Explanation-of-clib.json#uninstall


description: NCBI Prokaryotic Genome Annotation Pipeline (PGAP) input metadata (submol) JSON/YAML configuration file

$id: /$schema

title: Schema

description: The value of this keyword MUST be a URI (containing a scheme) and this URI MUST be normalized.

title: Consortium

description: Name of the project that generated the genome assembly

title: Free text comment about the genome assembly

description: Appears in the COMMENT section of each GenBank sequence record.

examples: This draft WGS assembly was generated by running SKESA to generate a de-novo assembly. The de-novo assembly was then concatenated with  configs generated using a guided assembler using antimicrobial resistance genes as baits to comprehensively catalog the set of resistance genes in the isolate. Note, some parts of the configs derived from the guided assembler may overlap de-novo configs, and other guided assembler configs. De-novo configs can be differentiated from guided assembler configs by their names, which include either 'denovo' or 'guided'.

title: Reserved

description: NCBI internal flag used for testing.

title: SRA assembly data

description: Sequence reads used to build the assembly

title: SRA Accession

description: Sequence Read Archive (SRA) accession for the run (with SRR, ERR or DRR prefix)

title: Author(s) of the genome assembly

description: Optional, but include if intending to submit to GenBank. Authors can be different from the contact.

title: First name

title: Last name

title: First letter of middle name

title: BioProject ID (PRJXX) for the project, if available

title: BioSample ID (SAMXXX) for the sequenced sample, if available

title: Submitter contact information

description: Optional, but include if intending to submit to GenBank. The main contact for this genome assembly.

required: organization department city country street email first_name last_name postal_code

title: State or region

examples: MD Florida

title: Fax number

title: City

title: Country

title: Department or division submitting the genome assembly

title: Email address

title: First name

title: First letter of middle name

title: Last name

title: Organization or consortium submitting the genome assembly

examples: Institute of Klebsiella foobarensis research

title: Phone number

title: Postal code

title: Street address

title: Class of input type

title: Location of input file

title: Locus tag prefix

description: One to 9-letter prefix to use for naming genes on this genome assembly. If an official locus tag prefix was already reserved from an INSDC organization (GenBank, ENA or DDBJ) for the given BioSample and BioProject pair, provide here. Otherwise, provide a string of your choice. If no value is provided, the prefix 'pgaptmp' will be used. See more details in this Note about locus tags at: https://github.com/ncbi/pgap/wiki/Input-Files#Note-about-locus-tags

title: Strain

description: Strain of the sequenced organism

title: Genus and species

description: Binomial name or, if the species is unknown, genus for the sequenced organism. This identifier must be valid in NCBI Taxonomy. See Taxonomy information for how to find out if the name is valid: https://github.com/ncbi/pgap/wiki/Input-Files#Taxonomy-information

title: Publication describing the genome assembly

title: Author(s)

title: First name

title: Last name

title: First letter of middle name

title: Publication status

description: Can be only one of: published, in-press, unpublished

enum: published in-press unpublished

title: PubMed ID for the publication

title: Title

examples: Discrete CHARMm of Klebsiella foobarensis. Journal of Improbable Results, vol. 34, issue 13, pages: 10001-100005, 2018

title: Topology of the sequences included in the fasta file

description: Possible values are linear or circular. Circular means that the first base in the sequence is adjacent to the last base. Please provide the topology in the metadata YAML file only if it is applicable to ALL sequences in the fasta file. If some sequences in the assembled genome are circular and others linear, include the topology in the definition line of each sequence in the fasta file with the tag value pair [topology=circular] or [topology=linear], after the SeqID and a space (e.g. >seq1 [topology=circular]). If the topology is provided in neither the metadata YAML nor the fasta file, the sequences will be presumed to be linear.

examples: circular linear

title: Location of the sequences included in the fasta file

description: Possible values are chromosome or plasmid. Please provide the location in the metadata YAML file only if it is applicable to ALL sequences in the fasta file. If some sequences in the assembled genome are chromosomes and others plasmids, include the location in the definition line of each sequence in the fasta file with the tag value pair [location=chromosome] or [location=plasmid], after the SeqID and a space (e.g. >seq1 [location=plasmid]). In plasmid case add [plasmid-name=<plasmidname>]. If the location is provided in neither the metadata YAML nor the fasta file, the sequences will be presumed to be chromosome. Note: since 2021 releases of PGAPx this will affect noticeably the annotation on the molecule

examples: chromosome plasmid

title: NCBI PGAP submol YAML


adonisrc.schema.json

description: Is project written in Typescript or not

description: Http server exception handler namespace

description: The driver to use for assets bundling

enum: encore vite fake

enum: web console test repl

required: name files

required: typescript providers