Pragma Engine 0.0.52
January 25th, 2022
- Optional integrations:
- For any classes using the
MatchmakingStrategy
interface, you must define a new method to validate if a party can be put into matchmaking. - If you have existing custom portal development, you will need to migrate to the new portal
5.ext-webapp
structure.
- For any classes using the
Integrations #
- For any classes using the
MatchmakingStrategy
interface, you must define a new method to validate if a party can be put into matchmaking.- Description: Define a new method for
validate(matchmakingKey: ExtMatchmakingKey, matchmakingParty: MatchmakingParty)
.
- Description: Define a new method for
- If you have existing custom portal development, you will need to migrate to the new portal
5.ext-webapp
structure.Description: The portal
5.ext-webapp
structure has changed. Once the steps below are completed, all regular development is done under/web/packages/5-ext-webapp
.Steps:
- Rename
web/packages/5-ext-webapp
toweb/packages/5-ext-webapp_initial
. - Create a new
5-ext-webapp
:$ cd platform && make portal-ext-create
- Bring your custom code over by replacing the entire
/web/packages/5-ext-webapp/src
folder withweb/packages/5-ext-webapp_initial/app/src
. - Update the config files by replacing the
/web/packages/5-ext-webapp/public/config
folder withweb/packages/5-ext-webapp_initial/app/public/config
. - (optional) If needed, add your extra dependencies to
/web/packages/5-ext-webapp/package.json
, then run:run npm install
- Rename
Additional information: We’ve added a new
make
command for building the ext portal for CI. This will create a bundle ready to be deployed underplatform/web/packages/5-ext-webapp/build
.$ cd platform $ make ci-portal-ext
For development, start the server in
/web/packages/5-ext-webapp
with:npm run start
For more information, read the
README_PORTAL.md
file.
Deprecations #
- none