Skip to content

SPIKE: Use custom events to trigger Scratch behaviour from the outside #3

SPIKE: Use custom events to trigger Scratch behaviour from the outside

SPIKE: Use custom events to trigger Scratch behaviour from the outside #3

Triggered via pull request February 5, 2025 11:54
Status Failure
Total duration 25s
Artifacts

commitlint.yml

on: pull_request
commitlint
14s
commitlint
Fit to window
Zoom out
Zoom in

Annotations

1 error
commitlint
You have commit messages with errors ⧗ input: Allow handleClickSave() to be triggered from outside MenuBar By listening for the custom `scratch-gui-save` event. Try this by: - Running `npm start` - Visiting http://localhost:8601 to view the Scratch editor - Execute `window.dispatchEvent(new Event('scratch-gui-save'));` in the web developer tools - Observe the `received scratch-gui-save` and `START_MANUAL_UPDATING` log messages in the web developer console ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Add button outside of Scratch GUI to fire save event ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: WIP: Add component to handle events sent from outside component ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ type must be lower-case [type-case] ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint