aurelien-brabant / ft_transcendance Goto Github PK

Currently, it is:

• in Chat src/nextjs-front/context/chat/ChatProvider.tsx

const socketIo = io("localhost:8080/chat");

• in Games hub src/nextjs-front/pages/hub.tsx

socket = io("localhost:8080/game");

localhost:8080 must be replaced in production

• Matches
• like env var
• separate function in a utils file

I will do a quick redesign of the dashboard layout using this tailwind UI template

• Messages made of spaces only should be cancelled
• Names should be trimmed (spaces removed at the beginning and at the end)

Looks like #50 don't build, according to the CI (which is apparently back, huray!)
See: https://app.circleci.com/pipelines/github/aurelien-brabant/ft_transcendance/82/workflows/80c57ef6-1947-4d47-ba0e-a182a894d7c2/jobs/67

If you click on the select menu (all/public/private/protected) which is an HTMLInputEvent, the chat position is reset to the top-left corner:

Like this:

See src/nextjs-front/components/Chat.tsx in <Draggable>

See: src/nestjs-back/src/chat/chat.gateway.ts WIP function handleSendPongInvite()

We want the achievements to be populated in database when the achievement module is initialized.
For that we will use NestJS's lifecycle events.

Note: we obviously don't want to duplicate achievements on each run. We only want to populate those that aren't already in database.

There are currently a ton of lint warnings when building the app.
We need to decrease this number as much as possible.

Branch: chat

File: src/nextjs-front/components/chat/GroupSettings.tsx

• Banned users shouldn't be able to access channels in which they were banned
• Muted users shoudn't be able to send messages in which they were muted

current

wanted

Integrate Punishment service with the chat and remove the former one.

When a game is over, the game is registered in the database but the player's data are not updated properly and so the leaderboard is also not updated

• Achievements Service?
• Or dump
• Or something else

Executed at start time

My profile background is darker whereas the user is on page Play.

Play should have the darker background.

• Power ups
• Maps (themes/background image)

This kind of message:

It's currently displayed using the websockets.

From the friends page using the button below:

You get:

User should be able to send invitations to play Pong to other users (by clicking on the Pong icon) from these two views:

• src/nextjs-front/components/chat/DirectMessage.tsx

• src/nextjs-front/components/chat/GroupUsers.tsx

While there is already an authentication system in place, it's somewhat broken and requires revisions.
Something based on a custom hook would be better.

Branch: chat

WIP #65

Branch: chat

WIP #65

• Implement some layout (grid?) with the current games on which the User can click in order to watch it
• Finish the layout for the matchmaking system

On master branch:

If user clicks on the left button to remove friend:

• Remove cron jobs
• New way to save banned and muted users in database

Documentation: Pipes | Gateways

Fix oauth redirect uri to redirect on port 8080
Do not display an error message unless an error has been reported when validating 42 login

New layout is: ft_transcendance/src/nextjs-front/components/layout/dashboard-layout.tsx

Then, to be removed:

• src/nextjs-front/components/DashboardLayout.tsx
• src/nextjs-front/components/DashboardSideNav.tsx
• The dashboardNavItems in src/nextjs-front/constants/nav.ts

• The User can watch any games currently running between 2 other users in real time.
• The User cannot interfere with the game.

⚠️ Depends on: #98 (wait for this PR to be merged before doing anything)

The seeder doesn't compile anymore (including in dev).

A user then has this kind of errors:

Currently API routes are, for the most part, not subject to any authentication/permission requirements.
We need to implement it.

NestJS provides the concept of guard for setting up such restrictions, so we will make use of them.

Note: for now we will ignore 2FA, we'll address this later.

Background doesn't match the entire container:

Typing zone should stick to the bottom but is not:

I have to replace this code which I commented to fix the user game stats update (see #165 ).