.creatomic
A config for Atomic Design 4 React generator
.creatomic
Validate
Check your file against this schema
Opens the validator with this schema already loaded. Paste your
.creatomic and it validates in your browser — nothing is uploaded.
Reference
Fields
Generated directly from the schema, following local
$refs, to two levels of nesting.
| Field | Type | Description |
|---|---|---|
tslint.enable | boolean | Control whether tslint is enabled for TypeScript files or not. default: true |
tslint.jsEnable | boolean | Control whether tslint is enabled for JavaScript files or not. default: false |
tslint.rulesDirectory | anyOf | An additional rules directory default: "" |
tslint.validateWithDefaultConfig | boolean | Validate a file when there is only a default tslint configuration is found default: false |
tslint.configFile | string | The path to the rules configuration file default: "" |
tslint.ignoreDefinitionFiles | boolean | Control if TypeScript definition files should be ignored default: true |
tslint.exclude | anyOf | Configure glob patterns of file paths to exclude from linting |
tslint.run | string | Run the linter on save (onSave) or on type (onType) default: "onType"one of: "onSave", "onType" |
tslint.nodePath | string | A path added to NODE_PATH when resolving the tslint module. default: "" |
tslint.autoFixOnSave | anyOf | Turns auto fix on save on or off, or defines which rules (e.g. `no-var-keyword`) to auto fix on save. default: false |
tslint.alwaysShowRuleFailuresAsWarnings | boolean | Always show rule failures as warnings, independent of the tslint configuration. default: false |
Audit
What we found in this schema
- Declared draft: draft-07
- Validates cleanly against its own meta-schema.
- Uses non-standard keywords that generic validators ignore:
annotations. - 11 properties, 100% carrying a description, max nesting depth 6.
Standards
Specification sections for the keywords in this schema
| Keyword | Document | Section |
|---|---|---|
$id | JSON Schema Core, draft 2020-12 | §8.2.1 — The "$id" Keyword |
$schema | JSON Schema Core, draft 2020-12 | §8.1.1 — "$schema" |
anyOf | JSON Schema Core, draft 2020-12 | §10.2.1.2 — "anyOf" |
default | JSON Schema Validation, draft 2020-12 | §9.2 — "default" |
description | JSON Schema Validation, draft 2020-12 | §9.1 — "title" and "description" |
enum | JSON Schema Validation, draft 2020-12 | §6.1.2 — "enum" |
items | JSON Schema Core, draft 2020-12 | §10.3.1.2 — "items" |
properties | JSON Schema Core, draft 2020-12 | §10.3.2.1 — "properties" |
type | JSON Schema Validation, draft 2020-12 | §6.1.1 — "type" |
Documents
- JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
- JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
- RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.
Source
Attribution
This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.