Sets prettier to run on the repo (#91379)

## About The Pull Request
Prettier (an auto formatter) is set to only run within the tgui folder
currently. This removes that limitation, allowing it to automatically
format all supported files in the repo (.js, .html, .yml
[etc](https://prettier.io/docs/))

I made a few exceptions for bundled and generated files
## Why It's Good For The Game
I'm of the opinion that code should look uniform and am lazy enough to
want CTRL-S to format files without having to think beyond that
## Changelog
This commit is contained in:
Jeremiah
2025-05-29 21:23:59 -07:00
committed by GitHub
parent ea0d60aecb
commit 9db2f6916b
419 changed files with 7001 additions and 6703 deletions

View File

@@ -7,14 +7,17 @@ The latest database version is 5.28; The query to update the schema revision tab
```sql
INSERT INTO `schema_revision` (`major`, `minor`) VALUES (5, 31);
```
or
```sql
INSERT INTO `SS13_schema_revision` (`major`, `minor`) VALUES (5, 31);
```
In any query remember to add a prefix to the table names if you use one.
-----------------------------------------------------
---
Version 5.30, 3 May 2025, by Atlanta-Ned
Adds a `manifest` table.
@@ -34,7 +37,8 @@ CREATE TABLE `manifest` (
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
```
-----------------------------------------------------
---
Version 5.30, 1 May 2025, by Rengan
Adds `crime_desc` field to the `citation` table to save the description of the crime.
@@ -42,7 +46,9 @@ Adds `crime_desc` field to the `citation` table to save the description of the c
ALTER TABLE `citation`
ADD COLUMN `crime_desc` TEXT NULL DEFAULT NULL AFTER `crime`;
```
-----------------------------------------------------
---
Version 5.29, 4 February 2024, by Tiviplus
Fixed admin rank table flags being capped at 16 in the DB instead of 24 (byond max)
@@ -52,7 +58,9 @@ ALTER TABLE `admin_ranks`
MODIFY COLUMN `exclude_flags` mediumint(5) unsigned NOT NULL,
MODIFY COLUMN `can_edit_flags` mediumint(5) unsigned NOT NULL;
```
-----------------------------------------------------
---
Version 5.28, 1 November 2024, by Ghommie
Added `fish_progress` as the first 'progress' subtype of 'datum/award/scores'
@@ -64,9 +72,12 @@ CREATE TABLE `fish_progress` (
PRIMARY KEY (`ckey`,`progress_entry`)
) ENGINE=InnoDB;
```
-----------------------------------------------------
---
Version 5.27, 26 April 2024, by zephyrtfa
Add the ip intel whitelist table
```sql
DROP TABLE IF EXISTS `ipintel_whitelist`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
@@ -78,29 +89,37 @@ CREATE TABLE `ipintel_whitelist` (
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
```
-----------------------------------------------------
---
Version 5.26, 03 December 2023, by distributivgesetz
Set the default value of cloneloss to 0, as it's obsolete and it won't be set by blackbox anymore.
```sql
ALTER TABLE `death` MODIFY COLUMN `cloneloss` SMALLINT(5) UNSIGNED DEFAULT '0';
```
-----------------------------------------------------
---
Version 5.25, 27 September 2023, by Jimmyl
Removes the text_adventures table because it is no longer used
```sql
DROP TABLE IF EXISTS `text_adventures`;
```
-----------------------------------------------------
---
Version 5.24, 17 May 2023, by LemonInTheDark
Modified the library action table to fit ckeys properly, and to properly store ips.
```sql
ALTER TABLE `library_action` MODIFY COLUMN `ckey` varchar(32) NOT NULL;
ALTER TABLE `library_action` MODIFY COLUMN `ip_addr` int(10) unsigned NOT NULL;
```
-----------------------------------------------------
---
Version 5.23, 28 December 2022, by Mothblocks
Added `tutorial_completions` to mark what ckeys have completed contextual tutorials.
@@ -113,14 +132,16 @@ CREATE TABLE `tutorial_completions` (
UNIQUE INDEX `ckey_tutorial_unique` (`ckey`, `tutorial_key`));
```
-----------------------------------------------------
---
Version 5.22, 22 December 2021, by Mothblocks
Fixes a bug in `telemetry_connections` that limited the range of IPs.
```sql
ALTER TABLE `telemetry_connections` MODIFY COLUMN `address` INT(10) UNSIGNED NOT NULL;
```
-----------------------------------------------------
---
Version 5.21, 15 December 2021, by Mothblocks
Adds `telemetry_connections` table for tracking tgui telemetry.
@@ -138,7 +159,8 @@ CREATE TABLE `telemetry_connections` (
UNIQUE INDEX `unique_constraints` (`ckey` , `telemetry_ckey` , `address` , `computer_id`)
);
```
-----------------------------------------------------
---
Version 5.20, 11 November 2021, by Mothblocks
Adds `admin_ckey` field to the `known_alts` table to track who added what.
@@ -148,7 +170,8 @@ ALTER TABLE `known_alts`
ADD COLUMN `admin_ckey` VARCHAR(32) NOT NULL DEFAULT '*no key*' AFTER `ckey2`;
```
-----------------------------------------------------
---
Version 5.19, 10 November 2021, by WalterMeldron
Adds an urgent column to tickets for ahelps marked as urgent.
@@ -156,7 +179,8 @@ Adds an urgent column to tickets for ahelps marked as urgent.
ALTER TABLE `ticket` ADD COLUMN `urgent` TINYINT(1) UNSIGNED NOT NULL DEFAULT '0' AFTER `sender`;
```
-----------------------------------------------------
---
Version 5.18, 1 November 2021, by Mothblocks
Added `known_alts` table for tracking who not to create suspicious logins for.
@@ -170,7 +194,8 @@ CREATE TABLE `known_alts` (
);
```
-----------------------------------------------------
---
Version 5.17, 8 October 2021, by MrStonedOne + Mothblocks
Changes any table that requrired a NOT NULL round ID to now accept NULL. In the BSQL past, these were handled as 0, but in the move to rust-g this behavior was lost.
@@ -189,7 +214,8 @@ ALTER TABLE `player` CHANGE `lastseen_round_id` `lastseen_round_id` INT(11) UNSI
ALTER TABLE `ticket` CHANGE `round_id` `round_id` INT(11) UNSIGNED NULL;
```
-----------------------------------------------------
---
Version 5.16, 31 July 2021, by Atlanta-Ned
Added `library_action` table for tracking reported library books and actions taken on them.
@@ -207,8 +233,8 @@ CREATE TABLE `library_action` (
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4;
```
---
-----------------------------------------------------
Version 5.15, 2 June 2021, by Mothblocks
Added verified admin connection log used for 2FA
@@ -224,7 +250,7 @@ CREATE TABLE `admin_connections` (
UNIQUE INDEX `unique_constraints` (`ckey`, `ip`, `cid`));
```
-----------------------------------------------------
---
Version 5.14, xx May 2021, by Anturke
Added exploration drone adventure table
@@ -241,7 +267,7 @@ CREATE TABLE `text_adventures` (
) ENGINE=InnoDB;
```
-----------------------------------------------------
---
Version 5.13, 30 April 2021, by Atlanta Ned
Added the `citation` table for tracking security citations in the database.
@@ -270,14 +296,14 @@ AUTO_INCREMENT=1
;
```
-----------------------------------------------------
---
Version 5.12, 29 December 2020, by Missfox
Modified table `messages`, adding column `playtime` to show the user's playtime when the note was created.
ALTER TABLE `messages` ADD `playtime` INT(11) NULL DEFAULT(NULL) AFTER `severity`
-----------------------------------------------------
---
Version 5.11, 7 September 2020, by bobbahbrown, MrStonedOne, and Jordie0608 (Updated 26 March 2021 by bobbahbrown)
@@ -291,7 +317,7 @@ ALTER TABLE `ticket`
ADD INDEX `idx_ticket_act_time_rid` (`action`, `timestamp`, `round_id`);
```
-----------------------------------------------------
---
Version 5.10, 7 August 2020, by oranges
@@ -320,7 +346,7 @@ ALTER TABLE `player` DROP COLUMN `discord_id`;
COMMIT;
```
-----------------------------------------------------
---
Version 5.9, 19 April 2020, by Jordie0608
Updates and improvements to poll handling.
@@ -363,7 +389,7 @@ $$
DELIMITER ;
```
-----------------------------------------------------
---
Version 5.8, 7 April 2020, by Jordie0608
Modified table `messages`, adding column `deleted_ckey` to record who deleted a message.
@@ -372,7 +398,7 @@ Modified table `messages`, adding column `deleted_ckey` to record who deleted a
ALTER TABLE `messages` ADD COLUMN `deleted_ckey` VARCHAR(32) NULL DEFAULT NULL AFTER `deleted`;
```
-----------------------------------------------------
---
Version 5.7, 10 January 2020 by Atlanta-Ned
Added ticket table for tracking ahelp tickets in the database.
@@ -394,7 +420,7 @@ CREATE TABLE `ticket` (
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
```
-----------------------------------------------------
---
Version 5.6, 6 December 2019 by Anturke
Added achievement_name and achievement_description columns to achievement_metadata table.
@@ -403,7 +429,7 @@ Added achievement_name and achievement_description columns to achievement_metada
ALTER TABLE `achievement_metadata` ADD COLUMN (`achievement_name` VARCHAR(64) NULL DEFAULT NULL, `achievement_description` VARCHAR(512) NULL DEFAULT NULL);
```
-----------------------------------------------------
---
Version 5.5, 26 October 2019 by Anturke
Added achievement_metadata table.
@@ -418,11 +444,11 @@ CREATE TABLE `achievement_metadata` (
) ENGINE=InnoDB;
```
-----------------------------------------------------
---
Version 5.4, 5 October 2019 by Anturke
Added achievements table.
See hub migration verb in _achievement_data.dm for details on migrating.
See hub migration verb in \_achievement_data.dm for details on migrating.
```sql
CREATE TABLE `achievements` (
@@ -434,7 +460,7 @@ CREATE TABLE `achievements` (
) ENGINE=InnoDB;
```
----------------------------------------------------
---
Version 5.3, 6 July 2019, by Atlanta-Ned
Added a `feedback` column to the admin table, used for linking to individual admin feedback threads. Currently this is only used for statistics tracking tools such as Statbus and isn't used by the game.
@@ -443,7 +469,7 @@ Added a `feedback` column to the admin table, used for linking to individual adm
ALTER TABLE `admin` ADD `feedback` VARCHAR(255) NULL DEFAULT NULL AFTER `rank`;
```
----------------------------------------------------
---
Version 5.2, 30 May 2019, by AffectedArc07
Added a field to the `player` table to track ckey and discord ID relationships
@@ -452,7 +478,8 @@ Added a field to the `player` table to track ckey and discord ID relationships
ALTER TABLE `player`
ADD COLUMN `discord_id` BIGINT NULL DEFAULT NULL AFTER `flags`;
```
----------------------------------------------------
---
Version 5.1, 25 Feb 2018, by MrStonedOne
Added four tables to enable storing of stickybans in the database since byond can lose them, and to enable disabling stickybans for a round without depending on a crash free round. Existing stickybans are automagically imported to the tables.
@@ -492,7 +519,7 @@ CREATE TABLE `stickyban_matched_cid` (
) ENGINE=InnoDB;
```
----------------------------------------------------
---
Version 5.0, 28 October 2018, by Jordie0608
Modified ban table to remove the need for the `bantype` column, a python script is used to migrate data to this new format.
@@ -533,21 +560,21 @@ CREATE TABLE `ban` (
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
```
----------------------------------------------------
---
Version 4.7, 18 August 2018, by CitrusGender
Modified table `messages`, adding column `severity` to classify notes based on their severity.
ALTER TABLE `messages` ADD `severity` enum('high','medium','minor','none') DEFAULT NULL AFTER `expire_timestamp`
----------------------------------------------------
---
Version 4.6, 11 August 2018, by Jordie0608
Modified table `messages`, adding column `expire_timestamp` to allow for auto-"deleting" messages.
ALTER TABLE `messages` ADD `expire_timestamp` DATETIME NULL DEFAULT NULL AFTER `secret`;
----------------------------------------------------
---
Version 4.5, 9 July 2018, by Jordie0608
Modified table `player`, adding column `byond_key` to store a user's key along with their ckey.
@@ -555,20 +582,20 @@ To populate this new column run the included script 'populate_key_2018-07', see
ALTER TABLE `player` ADD `byond_key` VARCHAR(32) DEFAULT NULL AFTER `ckey`;
----------------------------------------------------
---
Version 4.4, 9 May 2018, by Jordie0608
Modified table `round`, renaming column `start_datetime` to `initialize_datetime` and `end_datetime` to `shutdown_datetime` and adding columns to replace both under the same name in preparation for changes to TGS server initialization.
ALTER TABLE `round`
ALTER `start_datetime` DROP DEFAULT;
ALTER `start_datetime` DROP DEFAULT;
ALTER TABLE `round`
CHANGE COLUMN `start_datetime` `initialize_datetime` DATETIME NOT NULL AFTER `id`,
ADD COLUMN `start_datetime` DATETIME NULL DEFAULT NULL AFTER `initialize_datetime`,
CHANGE COLUMN `end_datetime` `shutdown_datetime` DATETIME NULL DEFAULT NULL AFTER `start_datetime`,
ADD COLUMN `end_datetime` DATETIME NULL DEFAULT NULL AFTER `shutdown_datetime`;
CHANGE COLUMN `start_datetime` `initialize_datetime` DATETIME NOT NULL AFTER `id`,
ADD COLUMN `start_datetime` DATETIME NULL DEFAULT NULL AFTER `initialize_datetime`,
CHANGE COLUMN `end_datetime` `shutdown_datetime` DATETIME NULL DEFAULT NULL AFTER `start_datetime`,
ADD COLUMN `end_datetime` DATETIME NULL DEFAULT NULL AFTER `shutdown_datetime`;
----------------------------------------------------
---
Version 4.3, 9 May 2018, by MrStonedOne
Added table `role_time_log` and triggers `role_timeTlogupdate`, `role_timeTloginsert` and `role_timeTlogdelete` to update it from changes to `role_time`
@@ -578,12 +605,15 @@ CREATE TABLE `role_time_log` ( `id` BIGINT NOT NULL AUTO_INCREMENT , `ckey` VARC
DELIMITER $$
CREATE TRIGGER `role_timeTlogupdate` AFTER UPDATE ON `role_time` FOR EACH ROW BEGIN INSERT into role_time_log (ckey, job, delta) VALUES (NEW.CKEY, NEW.job, NEW.minutes-OLD.minutes);
END
$$
CREATE TRIGGER `role_timeTloginsert` AFTER INSERT ON `role_time` FOR EACH ROW BEGIN INSERT into role_time_log (ckey, job, delta) VALUES (NEW.ckey, NEW.job, NEW.minutes);
END
$$
CREATE TRIGGER `role_timeTlogdelete` AFTER DELETE ON `role_time` FOR EACH ROW BEGIN INSERT into role_time_log (ckey, job, delta) VALUES (OLD.ckey, OLD.job, 0-OLD.minutes);
CREATE TRIGGER `role_timeTlogdelete` AFTER DELETE ON `role_time` FOR EACH ROW BEGIN INSERT into role_time_log (ckey, job, delta) VALUES (OLD.ckey, OLD.job, 0-OLD.minutes);
END
$$
DELIMITER ;
----------------------------------------------------
@@ -1003,3 +1033,4 @@ UPDATE erro_library SET deleted = 1 WHERE id = someid
(Replace someid with the id of the book you want to soft delete.)
----------------------------------------------------
$$