| commit | 2560578e1641780d2ce16d0dff8e936de93fc347 | [log] [tgz] |
|---|---|---|
| author | Ottomata <aotto@wikimedia.org> | Wed Jun 19 11:35:20 2024 -0400 |
| committer | Ottomata <aotto@wikimedia.org> | Thu Jun 20 09:39:33 2024 -0400 |
| tree | 95fbcd7810681bfb68bd0e3ce5671b55c369ef72 | |
| parent | b796d193225f5a036b65e7e25a067667e6d0c484 [diff] |
Make performer field optional in mediawiki/page/change/1.2.0 To do this without a major version bump, add an exception to skip backwards compatibility check for version 1.2.0 in .jsonschema-tools.yaml. This is needed because performer is not always set, especially in revision suppression case. Bug: T367923 Change-Id: I0790a902dfbbf3502b3202e9c0e52234eb894e1e
'Primary' event JSONSchemas for Wikimedia & MediaWiki event data.
This schema repository contains event schemas that directly affect user-facing features. These schemas are meant to represent 'tier 1' events. This repository complements the schemas/event/secondary repository.
See also:
NOTE: The only reason for having separate event schema repositories is to allow for different repository merge rights. Changes to primary schemas need to be more restricted than changes to secondary schemas.
Most files in this repo are automatically generated by jsonschema-tools and must not be changed after their initial creation.
Follow the Event Platform Schema Guidelines when creating or updating schemas.
Prerequisites:
npm install.To update a schema:
current.yaml file, and remember to increment the version in the $id field.npm run build-modified, which generates the versioned YAML and JSON files.To create a schema:
jsonschema/ namespace directories, and draft the first version in a new current.yaml file.npm run build-new path/to/your/current.yaml, which generates the versioned YAML and JSON files.