Chris-1010 9784ef8c67 PATCH: Username was not being accessed in chat.py: ...

The WebSockets used for chat do not maintain the same session context as regular HTTP routes and so, the username in Flask's session could not be accessed.

2025-02-01 03:14:24 +00:00

..

public/images

MAJOR Fix: Resolved API Request Delays;

2025-01-30 03:53:33 +00:00

src

PATCH: Username was not being accessed in chat.py:

2025-02-01 03:14:24 +00:00

Dockerfile

Refactored chat implementation to work with Websockets;

2025-01-25 15:29:17 +00:00

eslint.config.js

Update to structure

2025-01-23 12:13:50 +00:00

index.html

Minor Update: Input & Root Styles

2025-01-30 03:50:58 +00:00

package-lock.json

Refactored chat implementation to work with Websockets;

2025-01-25 15:29:17 +00:00

package.json

Refactored chat implementation to work with Websockets;

2025-01-25 15:29:17 +00:00

postcss.config.js

Update to structure

2025-01-23 12:13:50 +00:00

tailwind.config.js

FEAT: Floating Effect

2025-01-30 00:52:39 +00:00

tsconfig.app.json

Update to structure

2025-01-23 12:13:50 +00:00

tsconfig.json

Update to structure

2025-01-23 12:13:50 +00:00

tsconfig.node.json

Update to structure

2025-01-23 12:13:50 +00:00

vite.config.ts

UPDATE: Updated chat message structure;

2025-01-30 17:57:38 +00:00