Skip to content

Commit

Permalink
Consistent strings in yaml
Browse files Browse the repository at this point in the history
Signed-off-by: xibz <impactbchang@gmail.com>
  • Loading branch information
xibz authored and afrittoli committed May 15, 2024
1 parent 7c1c112 commit 095ee5f
Show file tree
Hide file tree
Showing 5 changed files with 16 additions and 8 deletions.
6 changes: 2 additions & 4 deletions .github/linters/.eslintrc.yml
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
plugins:
- jsonc
overrides:
- files:
- "schemas/*.json"
- "examples/*.json"
parser: "jsonc-eslint-parser"
- files: "*.json"
parser: jsonc-eslint-parser
rules:
# These are the set of rules that belong to jsonc. For more information,
# https://ota-meshi.github.io/eslint-plugin-jsonc/rules
Expand Down
12 changes: 11 additions & 1 deletion .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,20 @@ jobs:
uses: github/super-linter/slim@v4
env:
VALIDATE_ALL_CODEBASE: true
DEFAULT_BRANCH: main
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
VALIDATE_MARKDOWN: true
VALIDATE_JSON: true
# superlinter runs each linter on a per file bases and does not look
# at tool specific configuration to determine whether or not to the
# lint the given file.
#
# Due to that we need to globally include or exclude files. This also
# makes tools less flexible with one another in that if a tool
# requires a specific folder to be included and excluded, but other
# tools require must lint the excluded folder, then this pattern does
# not work. Instead superlinter cannot be used in that case, and the
# linter itself needs to be ran outside of superlinter.
FILTER_REGEX_INCLUDE: .*\/(custom|examples|schemas)\/.*

jsonschema:
name: Validate Schemas and Examples
Expand Down
2 changes: 1 addition & 1 deletion examples/incident_detected.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"context": {
"version": "0.5.0-draft",
"id": "F4BD2B55-B6F6-4F44-AF72-BD2D0E7A8708",
"chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"chainId": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"source": "/monitoring/prod1",
"type": "dev.cdevents.incident.detected.0.3.0-draft",
"timestamp": "2022-11-11T13:52:20.079Z"
Expand Down
2 changes: 1 addition & 1 deletion examples/incident_reported.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"context": {
"version": "0.5.0-draft",
"id": "F4BD2B55-B6F6-4F44-AF72-BD2D0E7A8708",
"chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"chainId": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"source": "/monitoring/prod1",
"type": "dev.cdevents.incident.reported.0.3.0-draft",
"timestamp": "2022-11-11T13:52:20.079Z"
Expand Down
2 changes: 1 addition & 1 deletion examples/incident_resolved.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"context": {
"version": "0.5.0-draft",
"id": "F4BD2B55-B6F6-4F44-AF72-BD2D0E7A8708",
"chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"chainId": "4c8cb7dd-3448-41de-8768-eec704e2829b",
"source": "/monitoring/prod1",
"type": "dev.cdevents.incident.resolved.0.3.0-draft",
"timestamp": "2022-11-11T13:52:20.079Z"
Expand Down

0 comments on commit 095ee5f

Please sign in to comment.