fix #139 fix routing to profiles when already on a player profile

beyond-all-reason · Apr 1, 2023 · 803870d · 803870d
1 parent 7d33415
commit 803870d
Show file tree

Hide file tree

Showing 3 changed files with 40 additions and 29 deletions.
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -101,7 +101,7 @@
     "tsconfig-paths": "^4.1.2",
     "type-fest": "^3.5.6",
     "typescript": "^4.6.4",
-    "unplugin-vue-router": "^0.3.2",
+    "unplugin-vue-router": "^0.5.4",
     "uuid": "^9.0.0",
     "vite": "^4.0.4",
     "vite-electron-plugin": "^0.7.4",

diff --git a/src/renderer/views/profile/[id].vue b/src/renderer/views/profile/[id].vue
@@ -26,13 +26,15 @@ TODO:
 </template>
 
 <script lang="ts" setup>
+import { computed } from "vue";
+
 import Flag from "@/components/misc/Flag.vue";
 
 const props = defineProps<{
     id: string;
 }>();
 
-const user = api.session.getUserById(parseInt(props.id));
+const user = computed(() => api.session.getUserById(parseInt(props.id)));
 </script>
 
 <style lang="scss" scoped></style>