eum2o / planning-poker Goto Github PK

when the tab is refreshed in really quick succession, you join multiple times

The border of the right emoji is thicker than that of the left emoji. Please fix this to look more consistent.

It's also possible to redesign the whole headline, maybe even with images instead of emojis.

add some cool visual effect like particles in the case if everyone votes the same.

I require assistance in adding a test skeleton that can be used as a reference for writing additional test scenarios. It would be helpful to have a simple test case, such as a successful scenario that involves entering a user name and clicking on 'Join'. The problem is not about how to utilize Playwright to write tests but how to start the backend before each test (what I manually do with yarn backend) and close if after each test. If someone could provide support by setting up a basic testing framework with setup and teardown methods, it would be greatly appreciated.

We should fix this so that a browser-refresh just refreshes the content that is displayed according to the model status.

I created a test file (server.test.js) (run with yarn test:backend) and configured a GitHub action to run it, but it is currently not functional since I couldn't start the backend and establish communication.

Maybe someone can help me out and add a very basic happy day test case (e.g. for "addUser") which I can use as an example to write further test cases.

add tooltips for the ✂🤷‍♀️🍵 buttons

When specifying your name with appending e.g. #SVNKoch you get to the join screen:

it would be nice if you would auto join with the specified name

The current version of the app only supports a single estimation session for all users, which prevents multiple teams from estimating in parallel. We need to address this limitation by implementing a solution that allows for multiple concurrent sessions.

We could implement multiple rooms that users can join by selecting from a list. Users could also create new rooms with optional password protection. Only the user who created a room or those who know the password would be able to delete it. Additionally, we could include a timeout feature to automatically delete rooms after a period of inactivity.

The server.js currently uses

• https://expressjs.com/de/ on port 5000 to receive data from clients
• https://socket.io/ on port 3001 to send data to clients

Since https://socket.io/ supports bi-directional communication, replacing express with socket.io would reduce the number of ports and dependencies, as well as simplify the setup.

When you cannot use the standard port - e.g. app port (5000) and you need to change it, you actually need to do that twice in order to get the app working with the server:

• in server.js and
• in constants.js

We should have exactly one place to specify that one.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update all dependencies (jest, react-icons, react-tooltip)
• Update all dependencies (major) (@testing-library/jest-dom, @testing-library/react, @testing-library/user-event, actions/checkout, node, web-vitals)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Automatically remove disconnected users to avoid consensus issues.

Currently, if a user disconnects, the estimations of that user are missing, preventing the remaining users from reaching consensus. As a workaround, all users need to be reset and rejoin. Automatically removing disconnected users will solve this issue.

• The server.js currently only allows to reset all users. It needs to be extended to allow removing a particular user.
• The client app needs to call the new method on disconnect.

Add a link to this GitHub repo in the UI. For example in the footer or whatever looks good.

Motivation: Users using this app can quickly jump to this repo to create issues or to contribute.

Scenario

GIVEN submit-name-view is displayed
WHEN user submits their name and hits ENTER
WHEN browser-refresh was performed
THEN user can still make their estimation-selection

Last step is broken: all estimation-cards are locked-away.

We should fix this. 😉