Skip to content

Commit 248cc2e

Browse files
Abh1noobAbh1noob
authored
Initial commit
0 parents  commit 248cc2e

32 files changed

Lines changed: 5112 additions & 0 deletions

‎.env.example‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Since the ".env" file is gitignored, you can use the ".env.example" file to
2+
# build a new ".env" file when you clone the repo. Keep this file up-to-date
3+
# when you add new variables to `.env`.
4+
5+
# This file will be committed to version control, so make sure not to have any
6+
# secrets in it. If you are cloning this repo, create a copy of this file named
7+
# ".env" and populate it with your secrets.
8+
9+
# When adding additional environment variables, the schema in "/src/env.js"
10+
# should be updated accordingly.
11+
12+
# Example:
13+
# SERVERVAR="foo"
14+
# NEXT_PUBLIC_CLIENTVAR="bar"
15+
16+
NEXT_PUBLIC_BASEURL=https://jsonplaceholder.typicode.com

‎.eslintrc.cjs‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
/** @type {import("eslint").Linter.Config} */
2+
const config = {
3+
"parser": "@typescript-eslint/parser",
4+
"parserOptions": {
5+
"project": true
6+
},
7+
"plugins": [
8+
"@typescript-eslint"
9+
],
10+
"extends": [
11+
"next/core-web-vitals",
12+
"plugin:@typescript-eslint/recommended-type-checked",
13+
"plugin:@typescript-eslint/stylistic-type-checked"
14+
],
15+
"rules": {
16+
"@typescript-eslint/array-type": "off",
17+
"@typescript-eslint/consistent-type-definitions": "off",
18+
"@typescript-eslint/consistent-type-imports": [
19+
"warn",
20+
{
21+
"prefer": "type-imports",
22+
"fixStyle": "inline-type-imports"
23+
}
24+
],
25+
"@typescript-eslint/no-unused-vars": [
26+
"warn",
27+
{
28+
"argsIgnorePattern": "^_"
29+
}
30+
],
31+
"@typescript-eslint/require-await": "off",
32+
"@typescript-eslint/no-misused-promises": [
33+
"error",
34+
{
35+
"checksVoidReturn": {
36+
"attributes": false
37+
}
38+
}
39+
]
40+
}
41+
}
42+
module.exports = config;

‎.gitignore‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2+
3+
# dependencies
4+
/node_modules
5+
/.pnp
6+
.pnp.js
7+
8+
# testing
9+
/coverage
10+
11+
# database
12+
/prisma/db.sqlite
13+
/prisma/db.sqlite-journal
14+
db.sqlite
15+
16+
# next.js
17+
/.next/
18+
/out/
19+
next-env.d.ts
20+
21+
# production
22+
/build
23+
24+
# misc
25+
.DS_Store
26+
*.pem
27+
28+
# debug
29+
npm-debug.log*
30+
yarn-debug.log*
31+
yarn-error.log*
32+
.pnpm-debug.log*
33+
34+
# local env files
35+
# do not commit any .env files to git, except for the .env.example file. https://create.t3.gg/en/usage/env-variables#using-environment-variables
36+
.env
37+
.env*.local
38+
39+
# vercel
40+
.vercel
41+
42+
# typescript
43+
*.tsbuildinfo
44+
45+
# idea files
46+
.idea

‎.vscode/settings.json‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"tailwindCSS.experimental.classRegex": [
3+
["clsx\\(([^)]*)\\)", "[\"'`]([^\"'`]*).*?[\"'`]"],
4+
["cx\\(([^)]*)\\)", "[\"'`]([^\"'`]*).*?[\"'`]"]
5+
],
6+
"editor.formatOnSave": true,
7+
"editor.codeActionsOnSave": {
8+
"source.organizeImports": "explicit"
9+
}
10+
}

‎CODE_OF_CONDUCT.md‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders of **CodeChef-VIT** pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to creating a positive environment
18+
include:
19+
20+
- Using welcoming and inclusive language
21+
- Being respectful of differing viewpoints and experiences
22+
- Gracefully accepting constructive criticism
23+
- Focusing on what is best for the community
24+
- Showing empathy towards other community members
25+
26+
Examples of unacceptable behavior by participants include:
27+
28+
- The use of sexualized language or imagery and unwelcome sexual attention or
29+
advances
30+
- Trolling, insulting/derogatory comments, and personal or political attacks
31+
- Public or private harassment
32+
- Publishing others' private information, such as a physical or electronic
33+
address, without explicit permission
34+
- Sharing critical Pentest findings with public or putting in an issue
35+
- DOS Attack on any of our subdomains (subdomain.codechefvit.com)
36+
- Continous load testing is strictly not allowed
37+
- Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Our Responsibilities | Consequences of Unacceptable Behavior
41+
42+
Project maintainers are responsible for clarifying the standards of acceptable
43+
behavior and are expected to take appropriate and fair corrective action in
44+
response to any instances of unacceptable behavior.
45+
46+
Project maintainers have the right and responsibility to remove, edit, or
47+
reject comments, commits, code, wiki edits, issues, and other contributions
48+
that are not aligned to this Code of Conduct, or to ban temporarily or
49+
permanently any contributor for other behaviors that they deem inappropriate,
50+
threatening, offensive, or harmful.
51+
52+
## Scope
53+
54+
This Code of Conduct applies both within project spaces and in public spaces
55+
when an individual is representing the project or its community. Representation of a project may be
56+
further defined and clarified by project maintainers.
57+
58+
## Enforcement
59+
60+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
61+
reported by contacting the project team at `contact@codechefvit.com`. All
62+
complaints will be reviewed and investigated and will result in a response that
63+
is deemed necessary and appropriate to the circumstances. The project team is
64+
obligated to maintain confidentiality with regard to the reporter of an incident.
65+
66+
Project maintainers who do not follow or enforce the Code of Conduct in good
67+
faith may face temporary or permanent repercussions as determined by other
68+
members of the project's leadership.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series
87+
of actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or
94+
permanent ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within
114+
the community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the **Contributor Covenant**
119+
version 2.1, available at
120+
https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
121+
122+
For answers to common questions about this code of conduct, see the FAQ at
123+
https://www.contributor-covenant.org/faq.

‎CONTRIBUTING.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
## Contribution Guidelines
2+
3+
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
4+
5+
## How to contribute
6+
7+
- Decide which repository to contribute
8+
- Decide what to contribute
9+
- Fork the repo then clone it locally
10+
- Commit your work (You should create a new branch when you're doing development work that is somewhat experimental in nature.)
11+
- Create a **Pull Request**
12+
- Congrats 🎉 you have just contributed towards open source!
13+
14+
## What to contribute
15+
16+
- Find an open issue to tackle
17+
- Ask if you can help write a new feature
18+
- Add / Improve Unit Testing
19+
- Write tutorials for how a project can be used and add to the readme
20+
- Review code on other people’s submissions and help improving / finding vulnerabilities
21+
22+
## Making a PR
23+
24+
- Provide all the appropriate details asked in PR template
25+
- A pull request doesn’t have to represent finished work. It’s usually better to open a pull request early on, so others can watch or give feedback on your progress. Just mark it as a “WIP” (Work in Progress) in the subject line. You can always add more commits later.
26+
27+
## Opening an Issue
28+
29+
- Make use of an appropriate Issue Template
30+
- We welcome Feature request, Bug Report, Documentation fix and others
31+
- Do not open critical security issues here, report them directly at [our email](mailto:contact@codechefvit.com).
32+
33+
## Communicating effectively
34+
35+
**Give context.** Help others get quickly up to speed. If you’re running into an error, explain what you’re trying to do and how to reproduce it. If you’re suggesting a new idea, explain why you think it’d be useful to the project (not just to you!).
36+
37+
```
38+
✔️ “X doesn’t happen when I do Y”
39+
❌ “X is broken! Please fix it.”
40+
```
41+
42+
**Do your homework beforehand.** It’s OK not to know things, but show that you tried. Before asking for help, be sure to check a project’s README, documentation, issues (open or closed), mailing list, and search the internet for an answer. People will appreciate when you demonstrate that you’re trying to learn.
43+
44+
```
45+
✔️ ““I’m not sure how to implement X. I checked the help docs and didn’t find any mentions.””
46+
❌ “How do I X?”
47+
```
48+
49+
**Keep requests short and direct.**
50+
51+
```
52+
✔️ “I’d like to write an API tutorial.”
53+
❌ “I was driving down the highway the other day and stopped for gas, and then I had this amazing idea for something we should be doing, but before I explain that, let me show you…“
54+
```
55+
56+
**It’s okay to ask questions (but be patient!).**
57+
58+
```
59+
✔️ “Thanks for looking into this error. I followed your suggestions. Here’s the output.”
60+
❌ “Why can’t you fix my problem? Isn’t this your project?”
61+
```
62+
63+
**Respect community decisions.**
64+
65+
```
66+
✔️ “I’m disappointed you can’t support my use case, but as you’ve explained it only affects a minor portion of users, I understand why. Thanks for listening.”
67+
❌ “Why won’t you support my use case? This is unacceptable!”
68+
```
69+
70+
## Misc
71+
72+
- You are welcome to Propose a new feature by creating an **Issue**.
73+
- You may Discuss a high-level topic or idea (for example, community, vision or policies) by writing to us at our [Email](mailto:contact@codechefvit.com).
74+
75+
## Attribution
76+
77+
- [Open Source Guide](https://opensource.guide/how-to-contribute/)

‎LICENSE‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2021 CodeChef-VIT
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

0 commit comments

Comments
 (0)