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

IgnisDa/issue1 #12

Merged
merged 70 commits into from
Nov 25, 2022
Merged

IgnisDa/issue1 #12

merged 70 commits into from
Nov 25, 2022

Conversation

IgnisDa
Copy link
Owner

@IgnisDa IgnisDa commented Nov 25, 2022

Fixes #1

Also show correct details non existent question
is requested.
Apparently due to changes in how node19 works as described in
https://nodejs.org/en/blog/announcements/v19-release-announce/#http-s-1-1-keepalive-by-default,
we need to add this header to fix the error: `FetchError: request
to http://0.0.0.0:8000/graphql failed, reason: socket hang up`.
This is just a skeleton. It does not work yet because it does not take into account the test case
that is displayed on the screen.
Also configure the website's typecheck command
to get the correct input files.
Instead of creating separate models for each test case data
type, we will store them all in a string and let the data
decide how to work with it. However, this method will result
in us losing the ability to do strict output comparisons (we have
implemented only  string based output correctness checking). I
do not think I am willing to give up such a big feature for a little
ease of db schema. However I will keep this in commit history
so that I can reference it later down the line.
@IgnisDa IgnisDa merged commit 8374c30 into main Nov 25, 2022
@IgnisDa IgnisDa deleted the IgnisDa/issue1 branch November 25, 2022 10:55
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.

Handle user input
1 participant