CHG Frontend Cleanup

[synoet]

The new web needs a nice scrubbing. lots of good stuff in there, but also some stuff that is outdated and some that should not be there.

[PIG208]

There is also a bunch of console.log hanging around there:

pig208@PIG:~/Anubis$ git grep -n console.log
old-web/src/Components/Admin/Assignment/LateExceptionAddCard.jsx:51:    console.log(date);
old-web/src/Components/Admin/IDE/ManagementIDEDialog.jsx:132:  console.log(images);
old-web/src/Components/Public/Blog/BlogPost.jsx:102:          .catch(((error) => console.log('FETCH/ERROR', error)));
old-web/src/Components/Public/Blog/BlogPost.jsx:104:      .catch((error) => console.log('IMPORT/ERROR', error));
old-web/src/Components/Public/IDE/IDEDialog.jsx:137:  console.log('STOP');
old-web/src/Components/Public/Questions/QuestionsCard.jsx:87:  console.log(responses);
old-web/src/index.js:14:// to log results (for example: reportWebVitals(console.log))
theia/proxy/index.js:68:        console.log(`cluster_ip ${row?.cluster_address}`)
theia/proxy/index.js:70:          console.log(`caching cluster ip ${row.cluster_address}`)
theia/proxy/index.js:86:    console.log(req.method, (new Date()).toISOString(), url.pathname, url.query);
theia/proxy/index.js:227:console.log("starting at 0.0.0.0:5000");
theia/proxy/index.js:228:console.log(`SECRET_KEY = ${SECRET_KEY}`);
web/src/Components/Admin/Assignment/LateExceptionAddCard.jsx:51:    console.log(date);
web/src/Components/Public/Blog/BlogPost.jsx:102:          .catch(((error) => console.log('FETCH/ERROR', error)));
web/src/Components/Public/Blog/BlogPost.jsx:104:      .catch((error) => console.log('IMPORT/ERROR', error));
web/src/Components/Public/IDE/IDEDialog.jsx:137:  console.log('STOP');
web/src/Components/Public/Questions/QuestionsCard.jsx:87:  console.log(responses);
web/src/Pages/Public/Assignment/Assignment.jsx:55:      console.log(error);
web/src/Pages/Public/Assignment/Assignment.jsx:65:    }).catch((error) => console.log(error));
web/src/Pages/Public/Course/Course.jsx:31:      console.log(data?.course);
web/src/Pages/Public/Courses/Courses.jsx:46:      console.log(data.courses);
web/src/Pages/Public/Courses/Courses.jsx:60:  console.log(courses);
web/src/Pages/Public/Submission/Submission.jsx:107:  console.log(submission);
web/src/index.js:14:// to log results (for example: reportWebVitals(console.log))

[wabscale]

Yeah those log statements have been in the frontend from the beginning. Maybe we should use some wrapper or something that will only actually print stuff if it is running in the react-scripts server. Alternatively, do either of you have any libraries or anything that does this already?

[PIG208]

Adding a wrapper to check process.env.NODE_ENV === "production" should be enough. We can have a hook for this custom logger, but maybe not all those log messages should be kept.

[wabscale]

ab84111

[PIG208]

There are some leftovers in the following files:

old-web/src/Components/Public/Blog/BlogPost.jsx
web/src/Components/Public/Blog/BlogPost.jsx
web/src/Components/Public/IDE/IDEDialog.jsx

[wabscale]

The blog post ones are not debug lines and should stay. The web/src/Components/Public/IDE/IDEDialog.jsx I did miss.