-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APS Management Modal #1060
APS Management Modal #1060
Conversation
has name and profile picture with logout button
@@ -66,6 +66,7 @@ import NewInputSchemeModal from "./ui/modals/configuring/theme-editor/NewInputSc | |||
import AssignNewSchemeModal from "./ui/modals/configuring/theme-editor/AssignNewSchemeModal.tsx" | |||
import AnalyticsConsent from "./ui/components/AnalyticsConsent.tsx" | |||
import PreferencesSystem from "./systems/preferences/PreferencesSystem.ts" | |||
import APSManagementModal from "./ui/modals/APSManagementModal.tsx" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can someone explain to me the difference between different @
imports and seemingly relative imports? I understand that @
refers to a module (or the javascript / typescript equivalent. Essentially a directory or collection of files), but we seem to switch between using an @
and a ./
and I'm not familiar with why.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We specify what the @ ones point to in our tsconfig and vite config, and they make it easier to change imports if we were to do a refactor since we’d only need to change there (for the most part). I think we switch between them because our editors auto-import using relative imports and nobody bothers to change it. It might be worth going through everything at some point and standardizing it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, not too big of a deal but would be nice if everything was the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't really think of anything else to add to this panel. Definitely makes the logout much more clear. Could see how people would accidently log themselves out previously.
Description
Adds an APS modal that displays user information and includes a logout button. This opens instead of just logging out when clicking the APS button in the main HUD.
Objectives
Testing Done
JIRA Issue