camille500 / real-time-web Goto Github PK

It’s really awesome for now, but there’s still the issues I raised, and the things on your wish-list!

Would be nice to have a section in the readme documenting that a .env file is needed, and what to put in it!

The following form, inputs, and errors aren’t very helpful:

• 1 minuten en 15 seconden -> 1 minuut en 15 seconden
• 2 minuten en 1 seconden -> 2 minuten en 1 seconde
• 1 minuten en 60 seconden -> 2 minuten, this one is unrelated, but still...

When going offline, the timer still continues. After a few minutes, when coming back, new tweets appear (but not the ones sent in those minutes).

That’s a reasonable way to handle offline users, but maybe there’s more possible? Like showing that the user is offline? Showing that the counter and the average per minute may not be correct?

Either use a .env thing, or add a comment (possible even a console.warn) that this shouldn‘t be done in production!