Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/i18n banana #118

Open
wants to merge 179 commits into
base: main
Choose a base branch
from

Conversation

bluffcyclops
Copy link

No description provided.

HoldenA1 and others added 30 commits May 6, 2024 13:16
Updated the README.md so onboarding should be easier for us folks new to the project.
Added a section on using python for running a local webserver so you can
actually run the E2E tests on your own computer.

Added how to run ESLint. This is the last of the included scripts that was not
explicitly documented.
npm reported security vulnerabilities so I just ran `npm audit fix` to deal
with it.
Forgot to run prettier before commit...
Update the hardcoded URLs to go point to the correct places after the repo forking.

We may want to investigate if it's possible to make these links relative instead of absolute somehow.
Add our team introduction video.
Added link to the wiki. Also changed `check` to `checking` for consistency.
Added section to cache npm dependencies. Also use the later versions of checkout and specify usage of node v20.
See: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows

Also replaced npm install with npm ci as suggested in the setup-node documentation.
See: https://docs.npmjs.com/cli/v8/commands/npm-ci
The previous set up would only run the Jest tests post deployment to github
pages on the live website and deployments only occur on the `main` branch.
This will run a python webserver on the Github runner and run the tests on
that. Most important, all branches will now have testing run.
Run Tests on all branches; Update Github Action Dependencies
…lity

Previously `npm run docs` would result in an error, meaning it was impossible
to locally generate the JSDocs on your own computer. This is now fixed. In
addition, I've setup main.yml to use the same script for consistancy. The
JSDocs will look slightly different than before. Previously the `Minami` theme
was used, however usage of that requies taffy which allows attackers to access
any data items in the Taffy database. I don't think that's important to us,
since what's in there for the JSDocs should be public already but...
See https://nvd.nist.gov/vuln/detail/CVE-2019-10790#range-9035153
web-flow and others added 5 commits June 9, 2024 10:05
The back button in the how-to-use popup was borked in firefox. I saw
that commit `05dd123edbc70e45e6cb09dcdfcf77a7906bcca8` deletes the
width attribute from #close-button (the button in question) in
love-compatibility/styles.css, but then the width attriubte is just
inherited from common/styles.css. This fixes that by using unset.
Change text of Love Compatibility title from `Love Compatibility` to
`Love Compat` to make things fit. Kinda awful hack but it works!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.