-
Notifications
You must be signed in to change notification settings - Fork 40
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
MDLSITE-5739 mustache_lint: error when running on openjdk11 #198
Conversation
Validator v18.11.5 complains about it (info notice), and in fact, having lang attribute seems a good practice these days: https://www.w3.org/International/questions/qa-html-language-declarations#quickanswer
80de1a3
to
b710385
Compare
I think travis fails on https://github.com/moodlehq/moodle-local_ci/blob/master/mustache_lint/mustache_lint.sh#L30 (e.g. "11.0.2" > "1.8" 😉 ), will see tomorrow if it is possbile to do proper semver comparison. |
Also enables mysql (for Xenial needs to be explicitly specified)
843ac56
to
2ae4e56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Ruslan, nice stuff. And great to have it covered and working against more envs! Let's see the remaining little details...
How to upgrade vnu-jar: 1. Identify latest stable release at https://www.npmjs.com/package/vnu-jar 2. Amend version at package.json 3. Run npm upgrade 4. Commit changes.
Thinking more. May be we should group all mustache tests and run them in all available java environments, and not differentiate between trusty and xenial? |
Thanks @kabalin ! Just a couple of questions:
* note that, personally, i'm not sure, either, if it's worth testing it over multiple ubuntu distributions, it just doubles the running time when, by default, I'd expect things to continue working the same. But I don't oppose, just 1) above called my attention. Other than that 1), I'm happy with this one as is, tell me that do you think so we can advance it... Ciao :-) |
Any thought about that 1) above, @kabalin ? I had this completely forgotten, sorry, just arrived here today by coincidence (another PR). |
Hi @stronk7, sorry I missed the your first comment completely (I was on holidays most of June).
Changes will follow in a moment. UPD: for some reason commit I added is shown above this comment. |
Here we go, thanks! |
👍 |
More details:
As I can see, repo does not include
package-lock.json
, I guess this is intentional, as previously requirement was "^17.3.0" (any compatible version)? I do not use "^18.11.5" as it seems bring up unstable releases above that version when npm is initialised or updated. Perhaps we need to introducepackage-lock.json
to make sure that end user is using the same version which has been integration-tested here?