-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #29 from radicalxdev/modify/emulator-setup
Modify/emulator setup
- Loading branch information
Showing
10 changed files
with
148 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Code of Conduct | ||
We are committed to fostering a welcoming and inclusive environment for all contributors. | ||
|
||
Our Pledge | ||
We as contributors pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, level of experience, nationality, personal appearance, race, and religion. | ||
|
||
Our Standards | ||
Examples of behavior that contributes to creating a positive environment include: | ||
|
||
Using welcoming and inclusive language | ||
Being respectful of differing viewpoints and experiences | ||
Gracefully accepting constructive criticism | ||
Focusing on what is best for the community | ||
Showing empathy towards other contributors | ||
Examples of unacceptable behavior by participants include: | ||
|
||
The use of sexual language or imagery | ||
Personal attacks | ||
Trolling or insulting/derogatory comments | ||
Public or private harassment | ||
Publishing someone's private information, such as a physical or electronic address, without explicit permission | ||
Other conduct which could reasonably be considered inappropriate in a professional setting | ||
Enforcement Responsibilities | ||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project maintainers at rex@radicalx.co. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project maintainers are obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. | ||
|
||
Attribution | ||
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html. | ||
|
||
Contact info | ||
If you have any further questions regarding this Code of Conduct, please contact us at rex@radicalx.co. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# Contribution Guidelines | ||
|
||
Welcome to our repository! If you're looking to contribute, you're in the right place. This document provides a comprehensive guide on how to contribute to our project, including explanations of key concepts like Pull Requests (PRs) and code reviews, as well as a step-by-step process for making contributions. | ||
|
||
## Understanding Pull Requests and Code Reviews | ||
|
||
### What is a Pull Request (PR)? | ||
|
||
A Pull Request is a method used in version control systems to introduce changes to the repository. After you make changes in a branch of your fork, you can issue a PR. This is essentially a request to the repository maintainers to pull your changes into the official project. PRs are a pivotal component of collaborative development, allowing for discussion and review of code before it integrates into the main codebase. | ||
|
||
### What is a Code Review? | ||
|
||
A code review is a part of the PR process where other contributors and maintainers review your code. This practice ensures quality and consistency in the codebase and is a perfect opportunity to get feedback on your coding decisions. Code reviews help catch bugs, ensure best practices, and maintain the overall health of the codebase. | ||
|
||
## Contributing to the Project | ||
|
||
Follow these steps to contribute to our project: | ||
|
||
### Step 1: Fork the Repository | ||
|
||
Start by forking the repository. This creates a copy of the repo under your GitHub account, which is your private workspace where you can make changes without affecting the original project. | ||
|
||
### Step 2: Create a Feature Branch | ||
|
||
1. Clone your fork to your local machine: | ||
```bash | ||
git clone https://github.com/your-username/repository-name.git | ||
2. Navigate into the cloned directory:: | ||
```bash | ||
cd repository-name | ||
3. Create a new branch for your feature:: | ||
```bash | ||
git checkout -b feature-branch-name | ||
|
||
### Step 3: Make Changes | ||
Make the required changes in your feature branch. If you have your development environment setup properly, eslint will run and ensure your code passes all rules before your commits are accepted. | ||
|
||
### Step 4: Push Changes and Create a Pull Request | ||
1. Push your changes to your fork:: | ||
```bash | ||
git push origin feature-branch-name | ||
2. Go to your fork on GitHub and click "New Pull Request". | ||
3. Set the base repository's sandbox branch as the base branch and your feature branch as the compare branch. | ||
4. Fill in the details of the pull request and submit it. | ||
# Final Steps | ||
Once your PR is submitted, it will be reviewed by our Team. Participate in the discussion and make any required changes. Once your PR is approved, it will be merged into the sandbox branch for further integration testing before it becomes part of the main project. | ||
Thank you for contributing to our project! Your efforts help us build and refine a product that meets the needs of our community. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
// paste your firebase config object here | ||
const firebaseConfig = { | ||
apiKey: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_API_KEY, | ||
authDomain: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_AUTH_DOMAIN, | ||
projectId: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_PROJECT_ID, | ||
storageBucket: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_STORAGE_BUCKET, | ||
appId: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_APP_ID, | ||
measurementId: process.env.NEXT_PUBLIC_FIREBASE_MEASUREMENT_ID | ||
apiKey: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_API_KEY, | ||
authDomain: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_AUTH_DOMAIN, | ||
projectId: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_PROJECT_ID, | ||
storageBucket: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_STORAGE_BUCKET, | ||
appId: process.env.NEXT_PUBLIC_FIREBASE_CLIENT_APP_ID, | ||
measurementId: process.env.NEXT_PUBLIC_FIREBASE_MEASUREMENT_ID, | ||
}; | ||
|
||
// stop editing below this | ||
export default firebaseConfig; | ||
export default firebaseConfig; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
rules_version = '2'; | ||
|
||
// Craft rules based on data in your Firestore database | ||
// allow write: if firestore.get( | ||
// /databases/(default)/documents/users/$(request.auth.uid)).data.isAdmin; | ||
service firebase.storage { | ||
match /b/{bucket}/o { | ||
match /{allPaths=**} { | ||
allow read, write: if false; | ||
} | ||
} | ||
} |