Merge branch 'main' into MapFeature

.env.example

@@ -0,0 +1,10 @@
+FIREBASE_API_KEY=your-firebase-api-key
+FIREBASE_AUTH_DOMAIN=your-firebase-auth-domain
+FIREBASE_PROJECT_ID=your-firebase-project-id
+FIREBASE_STORAGE_BUCKET=your-firebase-storage-bucket
+FIREBASE_MESSAGING_SENDER_ID=your-firebase-messaging-sender-id
+FIREBASE_APP_ID=your-firebase-app-id
+EAS_PROJECT_ID=your-eas-project-id
+EXPO_UPDATES_URL=your-expo-updates-url
+RN_MAPBOX_MAPS_DOWNLOAD_TOKEN=your-rn-mapbox-maps-download-token
+RN_MAPBOX_ACCESS_TOKEN=your-rn-mapbox-access-token

.expo-shared/README.md

@@ -0,0 +1,11 @@
+> Why do I have a folder named ".expo-shared" in my project?
+
+The ".expo-shared" folder is created when running commands that produce state that is intended to be shared with all developers on the project. For example, "npx expo-optimize".
+
+> What does the "assets.json" file contain?
+
+The "assets.json" file describes the assets that have been optimized through "expo-optimize" and do not need to be processed again.
+
+> Should I commit the ".expo-shared" folder?
+
+Yes, you should share the ".expo-shared" folder with your collaborators.

.expo-shared/assets.json

@@ -0,0 +1 @@
+{}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.gitignore

@@ -8,6 +8,7 @@ node_modules/
 dist/
 web-build/
 eas.json
+google-services.json
 
 # Native
 *.orig.*

App.jsx

@@ -12,9 +12,14 @@ import NoInternet from "./src/screens/NoInternetScreen";
 import NetInfo from "@react-native-community/netinfo";
 import Mapbox from "@rnmapbox/maps";
 import { LocationProvider } from "./src/utils/context/LocationContext";
+import { NotificationProvider } from "./src/utils/context/NotificationContext.js";
+import Constants from "expo-constants";
+
+// AsyncStorage.clear();
 
 Mapbox.setAccessToken(
-	"pk.eyJ1Ijoic2FhZGFhbi1oYXNzYW4iLCJhIjoiY2x5MzFyZmg3MDMzZTJqczdhY2xydjc3eiJ9.tMsFRe3duBTeqeI8lwbugw"
+	Constants.expoConfig.extra.RN_MAPBOX_ACCESS_TOKEN ??
+		process.env.RN_MAPBOX_ACCESS_TOKEN
 );
 
 export default function App() {
@@ -51,14 +56,16 @@ export default function App() {
 
 	return (
 		<UserProvider>
-			<GestureHandlerRootView style={{ flex: 1 }}>
-				<PaperProvider theme={theme}>
-					<LocationProvider>
-						<StatusBar style='light' />
-						<AppNavigator />
-					</LocationProvider>
-				</PaperProvider>
-			</GestureHandlerRootView>
+			<NotificationProvider>
+				<LocationProvider>
+					<GestureHandlerRootView style={{ flex: 1 }}>
+						<PaperProvider theme={theme}>
+							<StatusBar style='light' />
+							<AppNavigator />
+						</PaperProvider>
+					</GestureHandlerRootView>
+				</LocationProvider>
+			</NotificationProvider>
 		</UserProvider>
 	);
 }

CODE_OF_CONDUCT.md

@@ -0,0 +1,119 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/),
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,77 @@
+# Contributing to Tutorify
+
+We appreciate your interest in contributing to Tutorify! Here’s how you can help make the project better.
+
+## How to Contribute
+
+### Reporting Issues
+
+If you find a bug or have a feature request, please [open an issue](https://github.com/Saadaan-Hassan/Tutorify/issues). Make sure to include a clear description of the problem or the feature you’re requesting.
+
+### Suggesting Enhancements
+
+If you have an idea for an enhancement or a new feature, please [open an issue](https://github.com/Saadaan-Hassan/Tutorify/issues) with a detailed description of your suggestion.
+
+### Contributing Code
+
+To contribute code, follow these steps:
+
+1. **Fork the Repository**
+
+   Click the "Fork" button at the top right of this repository to create your own copy.
+
+2. **Clone Your Fork**
+
+   ```bash
+   git clone https://github.com/Saadaan-Hassan/Tutorify.git
+   cd tutorify
+   ```
+
+3. **Create a New Branch**
+
+   Create a new branch for your changes:
+
+   ```bash
+   git checkout -b my-new-feature
+   ```
+
+4. **Make Your Changes**
+
+   Make your changes or add new features. Ensure your code adheres to our [code style guidelines](#code-style-guidelines).
+
+5. **Commit Your Changes**
+
+   Commit your changes with a clear, descriptive message:
+
+   ```bash
+   git add .
+   git commit -m "Add new feature or fix issue"
+   ```
+
+6. **Push Your Changes**
+
+   Push your changes to your fork:
+
+   ```bash
+   git push origin my-new-feature
+   ```
+
+7. **Open a Pull Request**
+
+   Go to the [Pull Requests](https://github.com/Saadaan-Hassan/Tutorify/pulls) section of the repository and open a new pull request. Provide a clear description of your changes.
+
+## Code Style Guidelines
+
+- Use **ESLint** and **Prettier** for code linting and formatting.
+- Follow the existing code style and structure.
+- Write meaningful commit messages and pull request descriptions.
+
+## Documentation
+
+If you update or add features, please ensure that the documentation in `README.md` is up-to-date. We also appreciate contributions to the documentation to make it clearer and more helpful.
+
+## Code of Conduct
+
+Please follow our [Code of Conduct](CODE_OF_CONDUCT.md) in all interactions related to the project.
+
+Thank you for contributing to Tutorify!