+
+
+
+```ts
+ts example here
+```
+
+ Note: The method uses role.roleId, not role.guid.
+
+
+
+
\ No newline at end of file
diff --git a/src/lib/taDocs/3-client-allFunctions.md b/src/lib/taDocs/3-client-allFunctions.md
index 4817816..70d0f58 100644
--- a/src/lib/taDocs/3-client-allFunctions.md
+++ b/src/lib/taDocs/3-client-allFunctions.md
@@ -10,6 +10,7 @@ The table below shows all of the functions of the taClient. From this point onwa
|addServer()|Add a CoreServer. You will probably never use this.|True|
|addTournamentPool()|Add a map pool to a tournament. This is the way a map pool can be created.|True|
|addTournamentPoolMaps()|Add maps to an already existing map pool.|True|
+|addTournamentRole()|Add a role to a tournament.|True|
|addTournamentTeam()|Add a team to a tournament. This will create a new team|True|
|addUserToMatch()|Add a user to a match. This is how a coordinator joins a match.|True|
|connect()|Connect to a TournamentAssistant Core Server. This is the main server, not the tournament.|True|
@@ -42,6 +43,7 @@ The table below shows all of the functions of the taClient. From this point onwa
|removeQualifierMap()|Remove a qualifier map from an already existing qualifier.|True|
|removeTournamentPool()|Remove a map pool from a tournament.|True|
|removeTournamentPoolMap()|Remove a map from an already existing map pool.|True|
+|removeTournamentRole()|Remove a role from a tournament.|True|
|removeTournamentTeam()|Remove a team from a tournament.|True|
|removeUserFromMatch()|Remove a user from a match.|True|
|returnToMenu()|Return the speciied players to the menu.|False|
diff --git a/src/lib/taDocs/3-client-intro.md b/src/lib/taDocs/3-client-intro.md
index bb67b97..cce6690 100644
--- a/src/lib/taDocs/3-client-intro.md
+++ b/src/lib/taDocs/3-client-intro.md
@@ -3,16 +3,40 @@ The `taClient`(client for short) is how most of the actions will be carried out.
The `stateManager` is the way you would fetch tournaments, get matches, or do anything related to getting specific data that does not require a database query. It is best if you are familiar with what methods it has and how you can use them.
-For the ease of this explanation let me provide an example:
+## Standard Response Object
+There are a couple of important notes for client responses. Since most client responses are async, they will return a promise. This will be shown as `Promise
+ Example: A direct example is not available, as this function is not used in ShyyTAUI.
+
+
+
+
+
+Let me provide an example of how the client is used in ShyyTAUI:
```ts
onMount(async() => {
// Check if the user is logged in
if ($authTokenStore) {
- // Using the client listen to events that will not be stored in the state, such as scores and song finish events
+ // Using the client listen for events that will not be stored in the state,
+ // such as scores and song finish events
client.on('realtimeScore', handleRealtimeScoreUpdate);
client.on('songFinished', handleSongFinished);
} else {
- // If the user is not authenticated, they will be thrown to the discord authentication page
+ // If the user is not authenticated,
+ // they will be thrown to the discord authentication page
window.location.href = "/discordAuth"
}
});
diff --git a/src/lib/taDocs/sample.md b/src/lib/taDocs/sample.md
index 63c4a39..05b09b4 100644
--- a/src/lib/taDocs/sample.md
+++ b/src/lib/taDocs/sample.md
@@ -13,6 +13,20 @@ Some more normal text...
+
+ Why is this important? TypeScript DOES NOT recognise these `packetType` objects, hence when dealing with responses we often use `as any` to get rid of type errors.
+
+
+
+
+
+
+ Will the stateManager be out-of-date? The stateManager automatically updates its state when a packet is received or sent, so no, you do not have to worry about out-of-date information being stored.
+
+
+
+
+
## Support
If you have any issues, please contact us through Discord or email
diff --git a/src/routes/+layout.svelte b/src/routes/+layout.svelte
index 4d6fbcd..cf5e553 100644
--- a/src/routes/+layout.svelte
+++ b/src/routes/+layout.svelte
@@ -7,6 +7,7 @@
let isAuthenticated = false;
let profileDropdownOpen = false;
+ let mobileMenuOpen = false;
let userProfile: { name: string; avatar?: string } | null = null;
onMount(() => {
@@ -25,6 +26,10 @@
profileDropdownOpen = !profileDropdownOpen;
}
+ function toggleMobileMenu() {
+ mobileMenuOpen = !mobileMenuOpen;
+ }
+
function logout() {
authTokenStore.set(null);
discordDataStore.set(null);
@@ -32,14 +37,27 @@
isAuthenticated = false;
userProfile = null;
profileDropdownOpen = false;
+ mobileMenuOpen = false;
goto('/');
}
function handleClickOutside(event: MouseEvent) {
const dropdown = document.querySelector('.profile-container');
+ const mobileMenu = document.querySelector('.mobile-menu');
+ const hamburger = document.querySelector('.hamburger-button');
+
if (dropdown && !dropdown.contains(event.target as Node) && profileDropdownOpen) {
profileDropdownOpen = false;
}
+
+ if (mobileMenu && !mobileMenu.contains(event.target as Node) &&
+ hamburger && !hamburger.contains(event.target as Node) && mobileMenuOpen) {
+ mobileMenuOpen = false;
+ }
+ }
+
+ function handleNavClick() {
+ mobileMenuOpen = false;
}
@@ -52,7 +70,8 @@
+ Note: This will be explained further in the 'State Manager' section, along with further behaviour descriptors. (most info will even be repeated)
+
+
-