Closed marohrdanz closed 5 months ago
@marohrdanz Does your comment about "My fork of the NG-CHM Artifacts" mean that you have built and tested those artifacts after the Prettier step?
FYI: the two force pushes to mary-dev were rebases to
@ChrisWakefield , I have tested:
Are there other tests I should perform? (maybe a topic for today's meeting).
This pull request
My fork of the NG-CHM Artifacts repo contains artifacts built from the changes in this PR: https://github.com/marohrdanz/NG-CHM-Artifacts
1. Prettier
Ran prettier with default options:
on WebContent/javascript/*.js and custom.js files.
I just got tired of trying to understand the code with variable formatting and indentation.
2. GitHub Action updates
This run of prettier changed the line in
CompatibilityManager.js
containing the version string fromto include leading whitespace:
I naively thought I could simply add leading whitspace in the action workflow that extracts the version number. E.g.:
However GitHub Actions remove leading whitespace from arguments, lolz.
So I updated the github action that extracts the version number from
CompatibilityManager.js
.I also updated these actions to avoid GitHub's warning that Node 16 is deprecated. These actions have been updated to Node 20.
These updates are reflected in their corresponding repo releases:
3. Third-party actions update
These version updates were inspired by the Node 16 deprecation warnings.