Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -316,15 +316,19 @@ Used by: `tamasfe/taplo`.

**`x-tombi-toml-version`**

Used by: `tombi-toml/tombi`.
Used by: `tombi-toml/tombi`. See [this](https://tombi-toml.github.io/tombi/docs/json-schema#x-tombi-toml-version) for details.

**`x-tombi-array-values-order`**

Used by: `tombi-toml/tombi`.
Used by: `tombi-toml/tombi`. See [this](https://tombi-toml.github.io/tombi/docs/json-schema#x-tombi-array-values-order) for details.

**`x-tombi-table-keys-order`**

Used by: `tombi-toml/tombi`.
Used by: `tombi-toml/tombi`. See [this](https://tombi-toml.github.io/tombi/docs/json-schema#x-tombi-table-keys-order) for details.

**`x-tombi-string-formats`**

Used by: `tombi-toml/tombi`. See [this](https://tombi-toml.github.io/tombi/docs/json-schema#x-tombi-string-formats) for details.

**`x-intellij-language-injection`**

Expand Down
1 change: 1 addition & 0 deletions cli.js
Original file line number Diff line number Diff line change
Expand Up @@ -505,6 +505,7 @@ async function ajvFactory(
'x-tombi-toml-version',
'x-tombi-array-values-order',
'x-tombi-table-keys-order',
'x-tombi-string-formats',
'x-intellij-language-injection',
'x-intellij-html-description',
'x-intellij-enum-metadata',
Expand Down
14 changes: 10 additions & 4 deletions src/api/json/catalog.json
Original file line number Diff line number Diff line change
Expand Up @@ -5628,6 +5628,12 @@
"fileMatch": ["**/.github/stale.yml"],
"url": "https://www.schemastore.org/stale.json"
},
{
"name": "Starfish",
"description": "Configuration file for Starfish",
"fileMatch": ["starfish.yml"],
"url": "https://raw.githubusercontent.com/veepee-oss/json-schema/refs/heads/main/starfish/1-latest/starfish-schema.json"
},
{
"name": "Starship",
"description": "Configuration file for Starship. Documentation: https://starship.rs",
Expand Down Expand Up @@ -6018,7 +6024,7 @@
},
{
"name": "ui5.yaml",
"description": "UI5 Tooling Configuration File (ui5.yaml)",
"description": "UI5 CLI Configuration File (ui5.yaml)",
"fileMatch": [
"ui5.yaml",
"*-ui5.yaml",
Expand All @@ -6027,11 +6033,11 @@
"ui5-dist.yaml",
"ui5-local.yaml"
],
"url": "https://sap.github.io/ui5-tooling/schema/ui5.yaml.json"
"url": "https://ui5.github.io/cli/schema/ui5.yaml.json"
},
{
"name": "ui5-workspace.yaml",
"description": "UI5 Tooling Workspace Configuration File (ui5-workspace.yaml)",
"description": "UI5 CLI Workspace Configuration File (ui5-workspace.yaml)",
"fileMatch": [
"ui5-workspace.yaml",
"*-ui5-workspace.yaml",
Expand All @@ -6040,7 +6046,7 @@
"ui5-workspace-dist.yaml",
"ui5-workspace-local.yaml"
],
"url": "https://sap.github.io/ui5-tooling/schema/ui5-workspace.yaml.json"
"url": "https://ui5.github.io/cli/schema/ui5-workspace.yaml.json"
},
{
"name": "UTAM Page Object",
Expand Down
7 changes: 7 additions & 0 deletions src/schemas/json/pyproject.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
"$comment": "there are multiple resources describing pyproject.toml. The canonical reference is at https://packaging.python.org/en/latest/specifications/declaring-project-metadata/, which refers to multiple proposals such as PEP 517, PEP 518 and PEP 621",
"x-tombi-toml-version": "v1.0.0",
"x-tombi-table-keys-order": "schema",
"x-tombi-string-formats": ["email", "uri"],
"additionalProperties": false,
"definitions": {
"projectAuthor": {
Expand Down Expand Up @@ -54,6 +55,7 @@
"items": {
"type": "string"
},
"uniqueItems": true,
"title": "Build system dependencies",
"description": "List of strings following the version specifier specification, representing dependencies required to execute the build system.",
"markdownDescription": "List of strings following the [version specifier specification](https://packaging.python.org/en/latest/specifications/version-specifiers/#version-specifiers), representing dependencies required to execute the build system.",
Expand Down Expand Up @@ -355,6 +357,7 @@
"items": {
"type": "string"
},
"uniqueItems": true,
"title": "Project keywords",
"description": "List of keywords or tags that describe the project. They could be used by search engines to categorize the project.",
"markdownDescription": "List of keywords or tags that describe the project. They could be used by search engines to categorize the project.",
Expand All @@ -371,6 +374,7 @@
"items": {
"type": "string"
},
"uniqueItems": true,
"title": "Applicable Trove classifiers",
"description": "List of [Trove classifiers](https://pypi.org/classifiers/) that describe the project. PyPI use the classifiers to categorize projects.",
"markdownDescription": "List of [Trove classifiers](https://pypi.org/classifiers/) that describe the project. PyPI use the classifiers to categorize projects.",
Expand Down Expand Up @@ -497,6 +501,7 @@
"items": {
"type": "string"
},
"uniqueItems": true,
"title": "Project mandatory dependency requirements",
"description": "An array of [dependency specifier](https://packaging.python.org/en/latest/specifications/dependency-specifiers/) strings, each representing a mandatory dependent package of the project.",
"markdownDescription": "An array of [dependency specifier](https://packaging.python.org/en/latest/specifications/dependency-specifiers/) strings, each representing a mandatory dependent package of the project.",
Expand Down Expand Up @@ -558,6 +563,7 @@
"optional-dependencies"
]
},
"uniqueItems": true,
"title": "Dynamic metadata values",
"description": "Specifies which keys are intentionally unspecified under `[project]` table so build backend can/will provide such metadata dynamically. Each key must be listed only once. It is an error to both list a key in `dynamic` and use the key directly in `[project]`.\nOne of the most common usage is `version`, which allows build backend to retrieve project version from source code or version control system instead of hardcoding it in `pyproject.toml`.",
"markdownDescription": "Specifies which keys are intentionally unspecified under `[project]` table so build backend can/will provide such metadata dynamically. Each key must be listed only once. It is an error to both list a key in `dynamic` and use the key directly in `[project]`.\nOne of the most common usage is `version`, which allows build backend to retrieve project version from source code or version control system instead of hardcoding it in `pyproject.toml`.",
Expand Down Expand Up @@ -833,6 +839,7 @@
"markdownDescription": "Each list item should be either:\n- [dependency specifiers](https://packaging.python.org/en/latest/specifications/dependency-specifiers/), or\n- table with a single key `include-group` which specifies another group name to include into this one",
"x-intellij-html-description": "<p>Each list item should be either:</p><ul><li><a href=\"https://packaging.python.org/en/latest/specifications/dependency-specifiers/\">dependency specifiers</a>, or</li><li>table with a single key <code>include-group</code> which specifies another group name to include into this one</li></ul>",
"x-tombi-array-values-order": "version-sort",
"uniqueItems": true,
"items": {
"oneOf": [
{
Expand Down
7 changes: 2 additions & 5 deletions src/schemas/json/ruff.json
Original file line number Diff line number Diff line change
Expand Up @@ -1860,7 +1860,7 @@
]
},
"future-annotations": {
"description": "Whether to allow rules to add `from __future__ import annotations` in cases where this would simplify a fix or enable a new diagnostic.\n\nFor example, `TC001`, `TC002`, and `TC003` can move more imports into `TYPE_CHECKING` blocks if `__future__` annotations are enabled.\n\nThis setting is currently in [preview](https://docs.astral.sh/ruff/preview/) and requires preview mode to be enabled to have any effect.",
"description": "Whether to allow rules to add `from __future__ import annotations` in cases where this would simplify a fix or enable a new diagnostic.\n\nFor example, `TC001`, `TC002`, and `TC003` can move more imports into `TYPE_CHECKING` blocks if `__future__` annotations are enabled.",
"type": ["boolean", "null"]
},
"ignore": {
Expand Down Expand Up @@ -2454,6 +2454,7 @@
"ASYNC23",
"ASYNC230",
"ASYNC25",
"ASYNC250",
"ASYNC251",
"B",
"B0",
Expand Down Expand Up @@ -2989,9 +2990,6 @@
"PD1",
"PD10",
"PD101",
"PD9",
"PD90",
"PD901",
"PERF",
"PERF1",
"PERF10",
Expand Down Expand Up @@ -3741,7 +3739,6 @@
"UP035",
"UP036",
"UP037",
"UP038",
"UP039",
"UP04",
"UP040",
Expand Down
Loading