Fix cspell verify script to use the run script.
As part of investigating why the newest cspell version [causes
issues](https://github.com/flame-engine/flame/pull/3727) with the verify
script, I first notice that we don't run cspell with the correct flags
inside the verify script (notably not applying our own config file).
This fixes that by re-using the run script in the verify script, which
avoid repetition and future drift.
Co-authored-by: Lukas Klingsbo <me@lukas.fyi>
Fix alphabetization check in cspell verify script; it was using
non-bash-compliant code that would not actually work on certain systems;
in fact, it was not working on CI, which has caused some drift. This
also fixes the dictionaries.
Co-authored-by: Lukas Klingsbo <me@lukas.fyi>
Update shebang on cspell scripts to be more env agnostic.
This follows standard practices as seen in the [ysap
guide](https://style.ysap.sh/):
> Bash is not always located at /bin/bash, so use this line:
> `#!/usr/bin/env bash`
This is also in line with the other scripts on the repo.
The script has two purposes:
remove orphan words
alphabetize the files
I set it up to run on GitHub action as a checker, but a --fix option is available as well for running locally.
When running, I noticed that there are A LOT of orphaned words.
At first, I thought that it might be the case that cSpell was missing words on our docs that were clearly used, which would be a HUGE issue. I made this PR to validate that: #2735
But upon proper investigation, and using cSpell's trace command, I realized that we import multiple standard dictionaries: "en_US" and "softwareTerms", and they are constantly being updated. The word "cypher" was just added 12 hours ago, for example.
Turns out ALL of the current orphan words are properly being detected on our files, but now are included on the official dictionaries! Which is amazing.
Note that I did have to stop using the GitHub Action to run cSpell. The reason is twofold; (1) because I need to install cSpell anyway to run my script and didn't want to have the action download it again; and (2) because the version on the GitHub Action (even though it is the same 7.3.7 from npm that I have locally) doesn't have the latest updates (like does not have the cypher word that was added 12h ago). This would make my script and the CI script incompatible.
* Extracting dartdoc
* changing to dartdoc to tag
* extracting format action
* changing format action to tag
* extracting analyze action
* changing format action to tag
* extracting test action
* updating to use tag
* Script for handling publishing
* Use relative paths to Flame for bridge packages
* Publish flame_svg-1.0.0-rc5
* Publish flame_svg-1.0.0-rc5
* Real publish in script
* No slash at end of relative path
* Roll back svg changelog
* rc4 for svg
* Update fire atlas to use new position details
* Update usage of script
* Non-fullscreen ParallaxComponent
* Updated examples with no size needed
* Formatting
* Add docs for fullscreen parallax
* Fix formatting
* Remove need of nullable size
* Add basic parallax sizing test
* Fix formatting
* Remove unused imports
* Info text for the parallax examples
* Moving tutorials to the Flame main repository
* Update README.md
Co-authored-by: Jochum van der Ploeg <jochum@vdploeg.net>
* Upgraded scripts to support multi projects
* Removed comment out code
* Adding WIP disclaimer
Co-authored-by: Jochum van der Ploeg <jochum@vdploeg.net>