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.

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).
  • 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:

      1. Rename web/packages/5-ext-webapp to web/packages/5-ext-webapp_initial.
      2. Create a new 5-ext-webapp:
        $ cd platform && make portal-ext-create
        
      3. Bring your custom code over by replacing the entire /web/packages/5-ext-webapp/src folder with web/packages/5-ext-webapp_initial/app/src.
      4. Update the config files by replacing the /web/packages/5-ext-webapp/public/config folder with web/packages/5-ext-webapp_initial/app/public/config.
      5. (optional) If needed, add your extra dependencies to /web/packages/5-ext-webapp/package.json, then run: run npm install
    • 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 under platform/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