Skip to content

Commit 285f7c0

Browse files
INeedJobToStartWorkINeedJobToStartWork
committed
🚀 Init commit! :)
0 parents  commit 285f7c0

21 files changed

+5361
-0
lines changed

‎.env

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
ESLINT_USE_FLAT_CONFIG = true
2+
# JITI_ALIAS = {alias: {"@": "./src/"}}

‎.env.template

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
ESLINT_USE_FLAT_CONFIG = true

‎.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 100 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
name: "🐞 Report a bug"
2+
title: "🐞[BUG] - <TITLE_OF_ISSUE>"
3+
description: Create new report!
4+
labels: [bug]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thank you for taking the time to report a bug to FluiUI! 🙏
10+
11+
If you have a question about how to achieve something and are struggling, please post a question
12+
inside of either of the following places:
13+
- MyPlop's 💬[Discussion's tab](https://github.com/INeedJobToStartWork/MyPlop/discussions)
14+
15+
Before submitting a new bug/issue, please check the links below to see if there is a solution or question posted there already:
16+
- MyPlop's [Issue's tab]()
17+
- MyPlop's [closed issues tab]()
18+
- MyPlop's [Discussions tab]()
19+
20+
21+
Please fill in as much of the template below as you're able. If you don't know the answer to a question, that's okay, but please try to fill in as much as you can.
22+
It'll help us to triage your issue as quickly as possible.
23+
- type: input
24+
id: description
25+
attributes:
26+
label: Issue Description
27+
description: Please give a short description of the issue
28+
placeholder: Description title
29+
validations:
30+
required: true
31+
- type: input
32+
id: MyPlop_version
33+
attributes:
34+
label: MyPlop Version
35+
description: Which MyPlop version are you using?
36+
placeholder: e.g. v0.5.0
37+
validations:
38+
required: true
39+
- type: checkboxes
40+
id: MyPlop_latest
41+
attributes:
42+
label: Tested on Latest Version
43+
description: Check if this issue is reproducible with the latest version - it could be fixed.
44+
options:
45+
- label: "Yes"
46+
- type: input
47+
id: reproductionLink
48+
attributes:
49+
label: Reproduction
50+
description: Please provide a link to a reproduction on Github, CodeSandbox or StackBlitz.
51+
placeholder: |
52+
e.g. https://github.com/ineedjobtostartwork/xxx
53+
- type: textarea
54+
id: reproductionProcess
55+
attributes:
56+
label: Process to Reproduce bug
57+
description: Please provide steps to reproduce the bug.
58+
placeholder: |
59+
e.g.
60+
1. Go to '...'
61+
2. Click on '....'
62+
3. Scroll down to '....'
63+
4. See error
64+
- type: textarea
65+
id: reproductionImages
66+
attributes:
67+
label: Photo/Images Showing Bug
68+
description: |
69+
If applicable, please provide screenshots or photos showing the bug.
70+
More about github attachments limits: https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files.
71+
- type: textarea
72+
id: reproductionLogs
73+
attributes:
74+
label: Logs
75+
description: If applicable, please provide logs showing the bug (if exists).
76+
- type: textarea
77+
id: expectedBehavior
78+
attributes:
79+
label: What we got - What we expected
80+
description: What did you expect to happen? What happened instead?
81+
- type: textarea
82+
id: additionalContext
83+
attributes:
84+
label: Additional Context
85+
description: What did you wanted to do? Please provide any additional information here.
86+
- type: textarea
87+
id: triedFix
88+
attributes:
89+
label: What did you try to fix it?
90+
description: What did you try to fix it? Every information is useful.
91+
- type: textarea
92+
id: howSolved
93+
attributes:
94+
label: How did you solve it?
95+
description: How did you solve it? It's okay if you didn't solve it yet.
96+
- type: textarea
97+
id: possibleSolution
98+
attributes:
99+
label: How problem can be solved?
100+
description: If you have any idea, please share it with us.

‎.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: true
2+
contact_links:
3+
- name: 🤔 Long question or ideas?
4+
url: https://github.com/INeedJobToStartWork/MyPlop/discussions
5+
about: Ask long-form questions and discuss ideas.

‎.github/ISSUE_TEMPLATE/feature_request.yaml

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
name: "✨Idea - Feature Request"
2+
title: "✨[Idea] - <TITLE_OF_ISSUE>"
3+
description: Share your ideas with us!
4+
labels: [feature]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Wow, good to see you there!
10+
It's good to know you're creative ✨
11+
12+
Before submitting a new feature request, please check the links below to see if there somebody already requested it:
13+
- MyPlop's [Idea's tab]()
14+
- MyPlop's [closed ideas tab]()
15+
- MyPlop's [Discussions tab]()
16+
17+
Please fill in as much of the template below as you're able. If you don't know the answer to a question, that's okay, but please try to fill in as much as you can.
18+
- type: input
19+
id: idea
20+
attributes:
21+
label: Idea ✨
22+
description: Please give a short description of the feature
23+
placeholder: e.g. I want to add cooldown to button
24+
validations:
25+
required: true
26+
27+
- type: input
28+
id: work
29+
attributes:
30+
label: How it should work?
31+
description: Give a description of how it should work
32+
placeholder: |
33+
e.g After clicking button, it should be disabled for X seconds
34+
validations:
35+
required: true
36+
37+
- type: input
38+
id: solution
39+
attributes:
40+
label: What it gonna solve? Why we should ad it?
41+
description: How it will help you and others? What kind of problems it will solve?.
42+
placeholder: |
43+
e.g It will help me and users to prevent api calls spamming and give a better user experience.
44+
validations:
45+
required: true
46+
47+
- type: input
48+
id: implementation
49+
attributes:
50+
label: How it should be implemented?
51+
description: What do you expect, how it should be implemented? Which props?
52+
placeholder: |
53+
54+
validations:
55+
required: true
56+
57+
- type: input
58+
id: example
59+
attributes:
60+
label: Example of usage / I have seen it in other library
61+
description: |
62+
You can give a link to currently implemented feature in other library / give your own example.
63+
(Images, videos, code snippets, etc.)
64+
placeholder: |
65+
e.g Similar feature is implemented in XXX lib.
66+
Here is link: XXXX

‎.github/ISSUE_TEMPLATE/gdocs_report.yml

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
name: "📘 Docs issues"
2+
title: "📘 [issue] - <TITLE_OF_ISSUE>"
3+
description: What's wrong with our docs?
4+
labels: [issue]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thank you for taking the time to report a bug to MyPlop! 🙏
10+
11+
This report section is for reporting issues with the documentation. If you have a question about how to achieve something and are struggling, please post a question
12+
13+
14+
If you have a question about how to achieve something and are struggling, please post a question
15+
inside of either of the following places:
16+
- MyPlop's 💬[Discussion's tab](https://github.com/INeedJobToStartWork/MyPlop/discussions)
17+
18+
19+
Before submitting a new bug/issue, please check the links below to see if there is a solution or question posted there already:
20+
- MyPlop's [Issue's tab]()
21+
- MyPlop's [closed issues tab]()
22+
- MyPlop's [Discussions tab]()
23+
24+
25+
Please fill in as much of the template below as you're able. If you don't know the answer to a question, that's okay, but please try to fill in as much as you can.
26+
It'll help us to triage your issue as quickly as possible.
27+
28+
- type: input
29+
id: page
30+
attributes:
31+
label: Related page
32+
description: Which page/section is this issue related to?
33+
placeholder: e.g ReadMe.md line 10 - section "Installation"
34+
validations:
35+
required: true
36+
37+
- type: dropdown
38+
id: issue
39+
attributes:
40+
label: Kind of issue
41+
description: What kind of issue it is?
42+
multiple: true
43+
options:
44+
- "Unclear explanations"
45+
- "Missing information"
46+
- "Wrong information"
47+
- "Other"
48+
49+
- type: textarea
50+
id: description
51+
attributes:
52+
label: Issue Description
53+
description: Please give a short description of the issue
54+
55+
- type: textarea
56+
id: context
57+
attributes:
58+
label: Context
59+
description: Why did you come to this page? What were you trying to do?
60+
value: |
61+
I was trying to..., i come to this page because...
62+
63+
- type: dropdown
64+
id: rate
65+
attributes:
66+
label: Scale of problem
67+
description: How annoying is this issue?
68+
multiple: true
69+
options:
70+
- "1 - Not annoying"
71+
- "2 - A little annoying"
72+
- "3 - Annoying"
73+
- "4 - Very annoying"
74+
- "5 - Extremely annoying"
75+
- "6 - Unbearable"

‎.github/workflows/ci.yml

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
name: CI
2+
3+
on:
4+
push:
5+
branches: [main]
6+
pull_request:
7+
types: [opened, synchronize]
8+
9+
jobs:
10+
Continuous-Integration:
11+
runs-on: ubuntu-latest
12+
13+
steps:
14+
- uses: actions/checkout@v2
15+
- name: Setup Node.js
16+
uses: actions/setup-node@v2
17+
with:
18+
node-version: 20
19+
20+
- name: Setup pnpm
21+
uses: pnpm/[email protected]
22+
- name: Install dependencies
23+
run: pnpm install --no-frozen-lockfile
24+
- name: Format Files
25+
run: pnpm format
26+
- name: Linting Files
27+
run: pnpm lint:fix --force && pnpm lint --force
28+
- name: Building Files
29+
run: pnpm build
30+
- name: Start Files
31+
run: pnpm start

‎.prettierignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
*.hbs
2+
dist/*
3+
lib/*

‎CODE_OF_CONDUCT.md

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for
6+
everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity
7+
and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion,
8+
or sexual identity and orientation.
9+
10+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to a positive environment for our community include:
15+
16+
- Demonstrating empathy and kindness toward other people
17+
- Being respectful of differing opinions, viewpoints, and experiences
18+
- Giving and gracefully accepting constructive feedback
19+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
20+
- Focusing on what is best not just for us as individuals, but for the overall community
21+
22+
Examples of unacceptable behavior include:
23+
24+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
25+
- Trolling, insulting or derogatory comments, and personal or political attacks
26+
- Public or private harassment
27+
- Publishing others' private information, such as a physical or email address, without their explicit permission
28+
- Other conduct which could reasonably be considered inappropriate in a professional setting
29+
30+
## Enforcement Responsibilities
31+
32+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take
33+
appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive,
34+
or harmful.
35+
36+
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
37+
issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for
38+
moderation decisions when appropriate.
39+
40+
## Scope
41+
42+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing
43+
the community in public spaces. Examples of representing our community include using an official e-mail address, posting
44+
via an official social media account, or acting as an appointed representative at an online or offline event.
45+
46+
## Enforcement
47+
48+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible
49+
for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.
50+
51+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
52+
53+
## Enforcement Guidelines
54+
55+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem
56+
in violation of this Code of Conduct:
57+
58+
### 1. Correction
59+
60+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the
61+
community.
62+
63+
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation
64+
and an explanation of why the behavior was inappropriate. A public apology may be requested.
65+
66+
### 2. Warning
67+
68+
**Community Impact**: A violation through a single incident or series of actions.
69+
70+
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
71+
unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
72+
interactions in community spaces as well as external channels like social media. Violating these terms may lead to a
73+
temporary or permanent ban.
74+
75+
### 3. Temporary Ban
76+
77+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
78+
79+
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
80+
period of time. No public or private interaction with the people involved, including unsolicited interaction with those
81+
enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
82+
83+
### 4. Permanent Ban
84+
85+
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate
86+
behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
87+
88+
**Consequence**: A permanent ban from any sort of public interaction within the community.
89+
90+
## Attribution
91+
92+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at
93+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
94+
95+
Community Impact Guidelines were inspired by
96+
[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
97+
98+
[homepage]: https://www.contributor-covenant.org
99+
100+
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.
101+
Translations are available at https://www.contributor-covenant.org/translations.

0 commit comments

Comments
 (0)