Skip to content

Add Node.js to list of languages on README and demo languages - #2297

Open
pxpeterxu wants to merge 1 commit into
DMOJ:masterfrom
wanderlog:master
Open

Add Node.js to list of languages on README and demo languages#2297
pxpeterxu wants to merge 1 commit into
DMOJ:masterfrom
wanderlog:master

Conversation

@pxpeterxu

Copy link
Copy Markdown
Contributor

Motivation

Related to DMOJ/judge-server#1143:

After enabling support in judge-server for a Node.js-based executor, we need add the language to the demo instance and the documentation

Changes

  • Add JavaScript (Node.js) to the demo instance's languages list (language_all.json)
  • Add Node.js to the list of supported languages in the README

Testing

Ran python3 manage.py loaddata language_all and verified the languages were loaded properly in the Admin interface

image

Comment thread README.md Outdated
* GAS x86/x64/ARM
* Haskell
* INTERCAL
* JavaScript (Node.js, V8)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose for consistency with the C++ variants this should say "(Node.js and V8)".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to say Node.js and V8!

@pxpeterxu
pxpeterxu force-pushed the master branch 2 times, most recently from 9e9fcc7 to d93b90e Compare January 22, 2024 06:22
Comment thread judge/fixtures/language_all.json Outdated
"fields": {
"key": "NODEJS",
"name": "JavaScript (Node.js)",
"short_name": "Node.js",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The short name is used on the submission listing. For consistency, it should be all uppercase. If you leave it as null, then key will be used instead (which seems fine in this case).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call: I changed this to null, and the key should work well here

"pk": 77,
"fields": {
"key": "NODEJS",
"name": "JavaScript (Node.js)",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This naming sounds good to me -- could we also rename V8 to "JavaScript (V8)" for consistency?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to JavaScript V8!

@pxpeterxu

pxpeterxu commented Apr 6, 2025

Copy link
Copy Markdown
Contributor Author

Thanks for the review @Xyene and sorry about the extreme lateness of this follow-up. I just made the requested changes, so this should probably be good to go.

I'm not sure who's the best to merge this in, but @kiritofeng and @quantum5, might either of you be open to taking a quick look? (I see you've made some of the most recent merges)

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.72%. Comparing base (435839e) to head (9081526).
Report is 83 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2297      +/-   ##
==========================================
+ Coverage   46.78%   47.72%   +0.94%     
==========================================
  Files         251      260       +9     
  Lines       13309    13745     +436     
==========================================
+ Hits         6226     6560     +334     
- Misses       7083     7185     +102     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

3 participants