remove unrelated changes

Author: suanjiansalt

.github/pull_request_template.md

@@ -16,5 +16,5 @@ If you have not completed one of the steps below, you can create the pull reques
 When you have completed the checklist, press the "Ready for review" button.
 -->
 
--   [ ] I have run Prettier to reformat any changed files
--   [ ] I have verified my changes work
+- [ ] I have run Prettier to reformat any changed files
+- [ ] I have verified my changes work

components/candle/progressionService.ts

@@ -170,7 +170,7 @@ export class ProgressionService {
 
         const parentLocationId = subLocation
             ? subLocation.Properties?.ParentLocation
-            : location ?? contract.Metadata.Location
+            : (location ?? contract.Metadata.Location)
 
         if (!parentLocationId) {
             return
@@ -187,8 +187,8 @@ export class ProgressionService {
                 userProfile,
                 parentLocationId,
                 contractSession.gameVersion === "h1"
-                    ? contract.Metadata.Difficulty ?? "normal"
-                    : sniperUnlockable ?? undefined,
+                    ? (contract.Metadata.Difficulty ?? "normal")
+                    : (sniperUnlockable ?? undefined),
             )
 
             const maxLevel = masteryData?.MaxLevel || DEFAULT_MASTERY_MAXLEVEL

docs/CODE_OF_CONDUCT.md

@@ -17,24 +17,24 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
--   Demonstrating empathy and kindness toward other people
--   Being respectful of differing opinions, viewpoints, and experiences
--   Giving and gracefully accepting constructive feedback
--   Accepting responsibility and apologizing to those affected by our mistakes,
-    and learning from the experience
--   Focusing on what is best not just for us as individuals, but for the
-    overall community
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
 
 Examples of unacceptable behavior include:
 
--   The use of sexualized language or imagery, and sexual attention or
-    advances of any kind
--   Trolling, insulting or derogatory comments, and personal or political attacks
--   Public or private harassment
--   Publishing others' private information, such as a physical or email
-    address, without their explicit permission
--   Other conduct which could reasonably be considered inappropriate in a
-    professional setting
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Enforcement Responsibilities
 

docs/ESCALATION_GUIDELINES.md

@@ -6,18 +6,18 @@ and Peacock escalations.
 
 The guidelines:
 
--   Use localised strings for anything that isn't automatically localised by the game.
-    -   Try not to "re-localise" strings that are already in the game and available to us e.g. "No Disguise Change"
--   Try to "group" objectives together i.e. eliminations and retrieval objectives should be grouped separately (e.g. Target, Target, Target, Retrieval, Retrieval).
--   **Always** try to use `GroupObjectiveDisplayOrder` and keep objectives in the same order between levels (unless they've changed and need to be marked as new).
--   Use `IsNew` on any new objectives.
-    -   New objectives should be placed **before** old objectives in their groups.
-    -   The first level **should not** have any objectives marked as new.
--   Gamechangers **should always be placed to the right of main objectives**.
--   Try to have kill objectives first, before any other objectives.
--   Try to not put long strings for `BriefingName` this is so they show nicely in the tall tiles with scrolling/being truncated.
--   Don't use `LongBriefingText` unless it's absolutely required. It can be left out and it'll default to `BriefingText`.
--   Peacock escalations should be added **first** in locations **and in `EscalationCodenames.json`**.
--   If no conditions are included for a target, use the game to localise it (`UI_CONTRACT_GENERAL_OBJ_KILL`).
-    -   If conditions are included, include them in the HUD string and **LOCALISE IT**!
--   For `(Long)BriefingText`, try to use proper grammar (i.e. ending with a full stop).
+- Use localised strings for anything that isn't automatically localised by the game.
+    - Try not to "re-localise" strings that are already in the game and available to us e.g. "No Disguise Change"
+- Try to "group" objectives together i.e. eliminations and retrieval objectives should be grouped separately (e.g. Target, Target, Target, Retrieval, Retrieval).
+- **Always** try to use `GroupObjectiveDisplayOrder` and keep objectives in the same order between levels (unless they've changed and need to be marked as new).
+- Use `IsNew` on any new objectives.
+    - New objectives should be placed **before** old objectives in their groups.
+    - The first level **should not** have any objectives marked as new.
+- Gamechangers **should always be placed to the right of main objectives**.
+- Try to have kill objectives first, before any other objectives.
+- Try to not put long strings for `BriefingName` this is so they show nicely in the tall tiles with scrolling/being truncated.
+- Don't use `LongBriefingText` unless it's absolutely required. It can be left out and it'll default to `BriefingText`.
+- Peacock escalations should be added **first** in locations **and in `EscalationCodenames.json`**.
+- If no conditions are included for a target, use the game to localise it (`UI_CONTRACT_GENERAL_OBJ_KILL`).
+    - If conditions are included, include them in the HUD string and **LOCALISE IT**!
+- For `(Long)BriefingText`, try to use proper grammar (i.e. ending with a full stop).

docs/USER_PROFILES.md

@@ -16,17 +16,17 @@ If you are unsure, ask.
 
 Version 1 introduced the profile versioning system. The changes are:
 
--   Removed unused keys (non location parents) in `u.Extensions.progression.Locations`.
--   Upper-cased keys in `u.Extensions.progression.Locations` to fit with the rest of Peacock.
--   Added subpackages to certain locations in `u.Extensions.progression.Locations`:
-    -   Legacy profiles now have `normal` and `pro1`.
-    -   Sniper locations now have their unlockables contained inside the location.
--   Unused properties were removed from locations in `u.Extensions.progression.Locations`.
--   `u.Extensions.progression.Unlockables` has been removed.
+- Removed unused keys (non location parents) in `u.Extensions.progression.Locations`.
+- Upper-cased keys in `u.Extensions.progression.Locations` to fit with the rest of Peacock.
+- Added subpackages to certain locations in `u.Extensions.progression.Locations`:
+    - Legacy profiles now have `normal` and `pro1`.
+    - Sniper locations now have their unlockables contained inside the location.
+- Unused properties were removed from locations in `u.Extensions.progression.Locations`.
+- `u.Extensions.progression.Unlockables` has been removed.
 
 ## Version 2
 
 Version 2 introduced support for syncing official progress to Peacock. The changes are:
 
--   `u.Extensions.LastOfficialSync` has been added which records a date and time of the last official sync.
--   `u.Extensions.progression.PlayerProfileXp.Sublocations` has been changed to an object.
+- `u.Extensions.LastOfficialSync` has been added which records a date and time of the last official sync.
+- `u.Extensions.progression.PlayerProfileXp.Sublocations` has been changed to an object.

packaging/README.md

@@ -3,13 +3,13 @@
 This folder contains some tools related to the build/packaging/deployment
 infrastructure of the project.
 
--   `build.mjs` - The esbuild configuration for the server in production.
--   `buildTasks.mjs` - Pre-bundling of specific files.
--   `devLoader.mjs` - Starts the server in the development environment.
--   `esbuild-plugin-license.mjs` - esbuild plugin that automatically updates the
-    THIRDPARTYNOTICES.txt file.
--   `extractChallengeData.mjs` - a little CLI tool for downloading challenges from
-    the IOI servers.
--   `HOW_TO_USE.html` - legacy help file.
--   `json5ToJson.mjs` - Converts a JSON5 file to a JSON file with the same name (
-    but the JSON extension).
+- `build.mjs` - The esbuild configuration for the server in production.
+- `buildTasks.mjs` - Pre-bundling of specific files.
+- `devLoader.mjs` - Starts the server in the development environment.
+- `esbuild-plugin-license.mjs` - esbuild plugin that automatically updates the
+  THIRDPARTYNOTICES.txt file.
+- `extractChallengeData.mjs` - a little CLI tool for downloading challenges from
+  the IOI servers.
+- `HOW_TO_USE.html` - legacy help file.
+- `json5ToJson.mjs` - Converts a JSON5 file to a JSON file with the same name (
+  but the JSON extension).