/admin/maps/:mapID PATCH

[tsa96]

Same as #816, this one is really complicated, especially since there's so much to do when going to APPROVED.

[tsa96]

Some stuff from notes

Going to Approved

• Check that we actually have images, credits, everything we expect. The submitter can edit until this point (I think?)
• Body should include

  tracks: {  
    tier: number;  
    ranked: boolean;
  };  
  };
  }

  Frontend will have UI for choosing these based off of all the suggestions from submitter and testers. Then, for each gamemode of each track, create a Leaderboard entry - this will require the zoning refactor changes to be made to the DB schema. In short, a Leaderboard has a gamemode, where it's ranked or not, trackNum, and mapID. A map with "disabled" leaderboard just means Leaderboard entry doesn't exist.

Placeholders

See if we have anything in placeholders on MapSubmission. If so, iterate over each. Note that it's possible that during this period that same placeholder was created from another submission. I think we just have to accept that this could happen but not the end of the world, we could add support for merging two placeholders if needed

Activities

Created MAP_APPROVED activites for authors. Old code here:

const allCredits = await tx.mapCredit.findMany({
  where: { mapID, type: MapCreditType.AUTHOR }
});

await tx.activity.createMany({
  data: allCredits.map(
    (credit): Prisma.ActivityCreateManyInput => ({
      type: ActivityType.MAP_APPROVED,
      userID: credit.userID,
      data: mapID
    })
  )
});
}

[tsa96]

More from notes - I don't have further thought on this yet: make long-term issue for allows admins to revert map back to submission state? Maybe just SPECIAL? e.g. map gets added in fast for an event, but then wants to go back for approval after event

[tsa96]

When going to approved, take the last MapSubmissionVersion, rename it to the map's fileName and upload to maps/

[tsa96]

See #841 for some extra behaviour we need