Halit Aksoy
f5dcf930fa
- First visit logs in as a new guest through Keycloak without a form; the session, including an offline refresh token, is kept in local storage - Account menu on the home page: guests can log in or sign up, users can log out (which starts a new guest session) - The WebSocket client in core authenticates with the access token after connecting, reports "connected" once the server accepts it, and re-sends renewed tokens on the open connection - Game page shows player names; guests appear as "Guest 4F2A" - Auth channels, AuthUser and player names in UserConnectionInfo move to core and the backend uses them from there - Mobile keeps using userKey login for now |
||
|---|---|---|
| .. | ||
| src | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .prettierrc | ||
| jest.config.js | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| yarn.lock | ||
Mancala Core
This module contains common functionalities for the Mancala project.
Build
yarn build
Usage
Link this local package to other packages (backend, frontend, mobile).
yarn link
In the target package folder, run:
cd ../backend
yarn link @mancala/core
NPM Publish Instructions
Run the following commands:
npm login
npm publish --access public