Update packages and add github actions for tests#1271
Conversation
|
For the code coverage badge, we might have to reactivate code coverage at https://app.codecov.io/gh/mathjax/ using the admin account. |
dpvc
left a comment
There was a problem hiding this comment.
This all looks good. Thanks for doing it.
I am working on making the fonts use the scoped package, so that should make the temporary link for mathjax-full be unnecessary. I should have that shortly.
Also note that the current version of mathjax-newcm is 0.4.2-beta.8, but the package.json currently uses 0.4.0-beta.8. I don't think that will make any difference, but thought I should mention it anyway.
.github/workflows/test.js.yml
Outdated
| pnpm mjs:compile | ||
| components/bin/makeAll --mjs --terse --build components/mjs | ||
| pnpm cjs:compile | ||
| pnpm cjs:components:src:build | ||
| components/bin/makeAll --cjs --terse --build components/cjs | ||
| pnpm copy:pkg cjs |
There was a problem hiding this comment.
Would you be willing to use pnpm -s rather than just pnpm for these (and the ones below)? That way, you only see that script output rather than the pnpm commands themselves. I think that looks cleaner.
testsuite/jest.config.mjs
Outdated
| */ | ||
|
|
||
| import type {Config} from 'jest'; | ||
| // import type {Config} from 'jest'; |
There was a problem hiding this comment.
Remove this rather than comment out?
There was a problem hiding this comment.
Thanks. I meant to do that and forgot.
What do you think is best? I don't have strong feelings either way. |
|
I've made the v0.4.3-beta.8 releases of the fonts, so you might try switching to that and removing the |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
|
@dpvc I'll take care of your comments in a little while. |
I think it's good to be consistent. I will rename the files. |
I note that changing the font gets us back to the old values in |
|
For the record: |
That's pretty cool. Thanks for working that out.
Probably. I have been linking to the latest fonts, so the new values were probably in effect when I was writing all the TeX tests some months ago. I probably updated those tests at that time. But doing a
I was preparing a PR for that myself. The same change needs to be made in |
|
After this update, |
There's always something... I did not try linting, I thought that was running automatically via husky. |
PR primarily updates all packages and adds a github action to automatically run tests for PRs into
developbranch or when pushing directly todevelop. For all this it does quite a bit of housekeeping:Changes in Main Code
package.json,pnpm-lock.yamlMathtoolsTags.tsuflag, which needs target >ES6 inHtmlMethods.tsandUnicodeConfiguration.tsMenu.ts(we could do this by coercing withas unknown as Promise<void>if you don't like the emptythen.Changes in Test Code
package.json,pnpm-lock.yaml.mjsfile as.tsnow yields errors with latest typescript compilertsconfig.jsto includeDOMlibrary and update path for latestts-jestversionsetupTex.tsand include sources directly (as per our meeting).Update to tests
--from package script #1270Setoptions,Tagformat,Texhtmlas they throw errors in Linux. We could adapt the file names of the test to the same spelling. What do you think?Github Actions
.github/workflows. There were still a couple of things missing after our meeting, e.g., I had forgotten to compile the test helpers, the mjs files etc. I've ironed this all out now. As you can see tests are passing for this PR.