Update Github Action

Author: SolidKalium

.github/workflows/build-artifacts.yml

@@ -7,30 +7,50 @@ on:
   pull_request:
   workflow_dispatch:
 
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
 jobs:
   build:
     runs-on: ubuntu-latest
 
     steps:
       - name: Check out repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Set up Python
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: "3.x"
 
+      - name: Configure GitHub Pages
+        uses: actions/configure-pages@v5
+
       - name: Build artifacts
         run: python3 scripts/build_artifacts.py
 
-      - name: Upload demo page
-        uses: actions/upload-artifact@v4
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v6
         with:
-          name: test-page
-          path: dist/test.html
+          name: build-artifacts
+          path: dist/
 
-      - name: Upload MediaWiki export
-        uses: actions/upload-artifact@v4
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v4
         with:
-          name: mediawiki-export
-          path: dist/mediawiki-export.xml
+          path: dist/
+
+  deploy:
+    if: github.event_name != 'pull_request' && github.ref == 'refs/heads/main'
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

TODO.md

@@ -2,19 +2,20 @@
 
 * align usage documentation (specs, wiki doc page, visual test page)
   * Need to support at least on-wiki and on-web
-  * Need test cases to be a little more strategic? Maybe show js, nojs, and wiki all together? Not sure we really need a test case for every possible situation. It would be overwhelming.
 * improve visual test page
   * Support enter-your-own call to lua? (may need wasm Lua...)
   * rely on lua (either at build time or in the browser) instead of hardcoded lua outputs
     * Could have build-time lua be an optional step with cached output json
     * Would need shims for mw stuff
+  * Need test cases to be a little more strategic? Maybe show js, nojs, and wiki all together? Not sure we really need a test case for every possible situation. It would be overwhelming.
 * Link the export file for mediawiki to import
   * Figure out what MediaWiki:Gadgets-definition could look like if auto-imported.
   * How will MediaWiki handle "duplicate" pages?
 * audit code for readability and obviousness
   * Maybe do a little work to make styling and regional time formats be better supported?
-  * What timezone formats are supported as inputs?
+  * What timezone formats are supported as inputs? +8, UTC+8, etc?
   * error visibility when given a bad (or likely bad) input?
+    * Should add an error category tag and pass the input as output. If either start or end is bad, just do this.
 * Bugs
   * Tooltip supports click to open. Stays open when clicking again. Is that expected? Maybe close on second click? And/or just make it being open be tap only? Currently tabbable. Is that a good idea?
   * The server configs are hardcoded, but should live in json.