Fixed issue regarding not displaying user's registered name

.env.template

@@ -0,0 +1,13 @@
+NEXT_PUBLIC_FIREBASE_API_KEY=
+NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=
+NEXT_PUBLIC_FIREBASE_PROJECT_ID=
+NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=
+NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=
+NEXT_PUBLIC_FIREBASE_APP_ID=
+MEASUREMENT_ID=
+SERVICE_ACCOUNT_PROJECT_ID=
+SERVICE_ACCOUNT_PRIVATE_KEY=
+SERVICE_ACCOUNT_CLIENT_EMAIL=
+NEXT_PUBLIC_CLOUD_MESSAGING_SERVER_TOKEN=
+NEXT_PUBLIC_RESUME_UPLOAD_SERVICE_ACCOUNT=
+NEXT_PUBLIC_RESUME_UPLOAD_PASSWORD=

.eslintignore

@@ -1,9 +1,9 @@
-# Don't ever lint node_modules
-node_modules
-# Don't lint build output (make sure it's set to your correct build folder name)
-build
-# Don't lint nyc coverage output
-coverage
-
-# A temporary fix until rewrite is complete
-old
+# Don't ever lint node_modules
+node_modules
+# Don't lint build output (make sure it's set to your correct build folder name)
+build
+# Don't lint nyc coverage output
+coverage
+
+# A temporary fix until rewrite is complete
+old

.eslintrc

@@ -1,3 +1,3 @@
-{
-  "extends": ["next", "next/core-web-vitals", "prettier"]
-}
+{
+  "extends": ["next", "next/core-web-vitals", "prettier"]
+}

.gitattributes

@@ -0,0 +1,2 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto

.github/ISSUE_TEMPLATE/bug_report_issue_template.yml

@@ -1,62 +1,62 @@
-name: Bug Report
-description: File a bug report
-title: '[Bug] '
-labels: ['Type: Bug Report', 'Status: Awaiting Triage']
-assignees:
-  - abdullah50053
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this bug report! By giving as much detail as possible, you'll help us identify what went wrong and fixing the behavior.
-  - type: textarea
-    id: what-was-expected
-    attributes:
-      label: What did you expect to happen?
-      description: Describe the expected functionality of the feature/component.
-    validations:
-      required: true
-  - type: textarea
-    id: what-happened
-    attributes:
-      label: What happened?
-      description: |
-        Describe the behavior you encountered. Please be as detailed as possible.
-      placeholder: Tell us what you see!
-    validations:
-      required: true
-  - type: dropdown
-    id: scope
-    attributes:
-      label: Scope
-      description: What part of the project is this for?
-      options:
-        - Core
-        - Auth
-        - Admin/API
-        - Profile
-        - Registration
-        - Events
-        - Check-in
-        - HackerPack
-        - Judging
-        - Project Submissions
-    validations:
-      required: true
-  - type: dropdown
-    id: browsers
-    attributes:
-      label: What browsers are you seeing the problem on?
-      multiple: true
-      options:
-        - Firefox
-        - Chrome
-        - Safari
-        - Microsoft Edge
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: |
-        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
-      render: shell
+name: Bug Report
+description: File a bug report
+title: '[Bug] '
+labels: ['Type: Bug Report', 'Status: Awaiting Triage']
+assignees:
+  - abdullah50053
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! By giving as much detail as possible, you'll help us identify what went wrong and fixing the behavior.
+  - type: textarea
+    id: what-was-expected
+    attributes:
+      label: What did you expect to happen?
+      description: Describe the expected functionality of the feature/component.
+    validations:
+      required: true
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: |
+        Describe the behavior you encountered. Please be as detailed as possible.
+      placeholder: Tell us what you see!
+    validations:
+      required: true
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope
+      description: What part of the project is this for?
+      options:
+        - Core
+        - Auth
+        - Admin/API
+        - Profile
+        - Registration
+        - Events
+        - Check-in
+        - HackerPack
+        - Judging
+        - Project Submissions
+    validations:
+      required: true
+  - type: dropdown
+    id: browsers
+    attributes:
+      label: What browsers are you seeing the problem on?
+      multiple: true
+      options:
+        - Firefox
+        - Chrome
+        - Safari
+        - Microsoft Edge
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell

.github/ISSUE_TEMPLATE/feature_request_issue_template.md

@@ -1,25 +1,25 @@
----
-name: Feature Request
-about: Track or request a new feature.
-title: '[Feature] '
-labels: ['Type: Feature Request', 'Status: Awaiting Triage']
-assignees:
----
-
-# Overview
-
-[In a few sentences, this feature and the motivation behind it. What problems/
-issues will this feature solve/address?]
-
-# Proposal
-
-[Outline all tasks that need to be completed for this issue to be resolved. Feel
-free to create additional issues and link them here if the scope if this issue
-is large.]
-
-# Supplemental Information
-
-[Provide images or architecture diagrams of this new feature. Features with a
-larger scope must include diagrams or detailed descriptions to describe how they
-function. User-facing UI/UX must include mock-ups and descriptions to explain
-how they function.]
+---
+name: Feature Request
+about: Track or request a new feature.
+title: '[Feature] '
+labels: ['Type: Feature Request', 'Status: Awaiting Triage']
+assignees:
+---
+
+# Overview
+
+[In a few sentences, this feature and the motivation behind it. What problems/
+issues will this feature solve/address?]
+
+# Proposal
+
+[Outline all tasks that need to be completed for this issue to be resolved. Feel
+free to create additional issues and link them here if the scope if this issue
+is large.]
+
+# Supplemental Information
+
+[Provide images or architecture diagrams of this new feature. Features with a
+larger scope must include diagrams or detailed descriptions to describe how they
+function. User-facing UI/UX must include mock-ups and descriptions to explain
+how they function.]

.github/ISSUE_TEMPLATE/internal_issue_template.md

@@ -1,23 +1,23 @@
----
-name: Internal/Chore Task
-about: Track a chore task that isn't user-facing.
-title: '[Internal] '
-labels: ['Type: Internal/Chore', 'Status: Awaiting Triage']
-assignees:
----
-
-# Overview
-
-[In a few sentences, describe what the scope of the task. What problems/issues
-will these changes solve/address?]
-
-# Proposal
-
-[Outline all tasks that need to be completed for this issue to be resolved. Feel
-free to create additional issues and link them here if the scope if this issue
-is large.]
-
-# Supplemental Information
-
-[Provide architecture diagrams of this new feature. Tasks with larger scope must
-include diagrams or detailed descriptions to describe how they function.]
+---
+name: Internal/Chore Task
+about: Track a chore task that isn't user-facing.
+title: '[Internal] '
+labels: ['Type: Internal/Chore', 'Status: Awaiting Triage']
+assignees:
+---
+
+# Overview
+
+[In a few sentences, describe what the scope of the task. What problems/issues
+will these changes solve/address?]
+
+# Proposal
+
+[Outline all tasks that need to be completed for this issue to be resolved. Feel
+free to create additional issues and link them here if the scope if this issue
+is large.]
+
+# Supplemental Information
+
+[Provide architecture diagrams of this new feature. Tasks with larger scope must
+include diagrams or detailed descriptions to describe how they function.]

.github/ISSUE_TEMPLATE/refactor_issue_template.md

@@ -1,15 +1,15 @@
----
-name: Refactor
-about: Outline and track code that needs to be refactored.
-title: '[Refactor] '
-labels: ['Type: Refactor', 'Status: Awaiting Triage']
-assignees:
----
-
-# Overview
-
-[Why is this refactor happening? Describe the motivations.]
-
-# What Needs to Change
-
-[Specify all files that will be changed.]
+---
+name: Refactor
+about: Outline and track code that needs to be refactored.
+title: '[Refactor] '
+labels: ['Type: Refactor', 'Status: Awaiting Triage']
+assignees:
+---
+
+# Overview
+
+[Why is this refactor happening? Describe the motivations.]
+
+# What Needs to Change
+
+[Specify all files that will be changed.]

.github/config.yml

@@ -1,11 +1,11 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Project Discussion
-    url: https://github.com/acmutd/hackportal/discussions
-    about: Talk about general project features and ideas here.
-  - name: ACM Development
-    url: https://acmutd.co/teams/dev
-    about: More information about the core HackPortal maintainers.
-  - name: Inquiries for Maintainers
-    url: [email protected]
-    about: If you have a question specific to the maintainers, contact them here.
+blank_issues_enabled: false
+contact_links:
+  - name: Project Discussion
+    url: https://github.com/acmutd/hackportal/discussions
+    about: Talk about general project features and ideas here.
+  - name: ACM Development
+    url: https://acmutd.co/teams/dev
+    about: More information about the core HackPortal maintainers.
+  - name: Inquiries for Maintainers
+    url: [email protected]
+    about: If you have a question specific to the maintainers, contact them here.