blurtechlegacy / blurred-board Goto Github PK

Interactive component showing how much time is left before the end of the competition. The start and end times are in the component Timer.tsx

Need to deal with terminology and formulas.
Our test scoreboard: check.noctf.ru, sources: HackerDom/ctf-scoreboard-client
RuCTF 2019 scoreboard: ructfe.org/results
How is calculated: SLA, flagpoint, flags, score. It is advisable to explain this within the data coming from the server.

All requests and helpers for HTTP need to be rewritten without using classes. You also need to rewrite API requests and store services. For stor service methods, you need to write an abstraction.

It is necessary to implement getting the current state on web sockets and getting the whole story by timeout.

It is necessary to draw graphs on services by analogy with ructfe.org/results. It is advisable to use a lightweight library, for example d3. To perform, you need the calculated data from the task #19

Need to split huge board component to couples more less components due to solid responsibility

You need to make an animated skeleton loader for fields that may be empty. Those. even in the absence of data, everything should be rendered. Something like an indication that the data has not yet been downloaded, but will be loaded. Get inspired by the Facebook skeleton.

Requests that are too heavy do not have time to load and go again, although the previous one has not yet been completed. A request with 100 commands can weigh tens of megabytes. Perhaps it will be cheaper to write a layer between the backend and the frontend and continue to act somehow.

Need to handle network errors. So that if there is no data, the application does not crash. Signaled an error such as a notification.

Export either using Print API, or to an Excel and pdf file.

Document the api checker so that you can conveniently view the types and format of server requests and responses.

It is necessary not to make the next request until the previous one has been fulfilled or to prohibit new requests until the old ones are fulfilled.

Add data after calculation using formulas from #19

There was an idea to accompany events musically. For example:

• When your service has fallen sounds the sound of a pig from Kaspersky Anti-Virus 2006.
• The beginning of the competition is voiced by music from the program “What? Where? When?”, when they take out the black box.
• And other stupidity.

Create scripts for linting and checking build capabilities.

Wrap the app in Docker. Make Nginx give away a static build. At the same time, it is advisable to leave Heroku support so that you can deploy by button.

Fix displaying place, fix displaying time (and rewrite class), fix table markup.

Reduce subsequent page loading by placing data in the localstorage. During initialization, data will first of all be requested from there, written to the Redux state, and after that, fresh data will be requested. But part of the data will already be rendered.