@irfanshadikrishad/anilist 1.0.6 → 1.0.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/bin/helpers/auth.d.ts +2 -2
- package/bin/helpers/auth.js +49 -36
- package/bin/helpers/fetcher.js +2 -3
- package/bin/helpers/lists.d.ts +1 -1
- package/bin/helpers/lists.js +42 -64
- package/bin/helpers/more.d.ts +1 -1
- package/bin/helpers/more.js +112 -86
- package/bin/helpers/mutations.d.ts +1 -1
- package/bin/helpers/mutations.js +1 -1
- package/bin/helpers/queries.d.ts +5 -3
- package/bin/helpers/queries.js +13 -3
- package/bin/helpers/types.d.ts +111 -0
- package/bin/helpers/types.js +26 -0
- package/bin/helpers/workers.d.ts +9 -1
- package/bin/helpers/workers.js +403 -53
- package/bin/index.js +3 -2
- package/package.json +15 -4
- package/CHANGELOG.md +0 -10
- package/CODE_OF_CONDUCT.md +0 -43
- package/CONTRIBUTING.md +0 -75
package/CONTRIBUTING.md
DELETED
|
@@ -1,75 +0,0 @@
|
|
|
1
|
-
#### Contribution Guidelines
|
|
2
|
-
|
|
3
|
-
Thank you for considering contributing to **@irfanshadikrishad/anilist**! We welcome contributions from everyone and appreciate your interest in improving the project. Please follow the guidelines below to ensure a smooth contribution process.
|
|
4
|
-
|
|
5
|
-
#### How to Contribute?
|
|
6
|
-
|
|
7
|
-
#### 1. Fork the Repository
|
|
8
|
-
|
|
9
|
-
1. Click the "Fork" button in the top right corner of the repository page.
|
|
10
|
-
2. Clone your forked repository to your local machine:
|
|
11
|
-
```bash
|
|
12
|
-
git clone https://github.com/your-username/anilist.git
|
|
13
|
-
```
|
|
14
|
-
3. Navigate to the project directory:
|
|
15
|
-
```bash
|
|
16
|
-
cd anilist
|
|
17
|
-
```
|
|
18
|
-
4. Set Up the Development Environment
|
|
19
|
-
|
|
20
|
-
1. Install the required dependencies:
|
|
21
|
-
|
|
22
|
-
```bash
|
|
23
|
-
npm install
|
|
24
|
-
```
|
|
25
|
-
|
|
26
|
-
5. Create a New Branch
|
|
27
|
-
Create a new branch for your feature or bug fix:
|
|
28
|
-
```bash
|
|
29
|
-
git checkout -b feature/my-new-feature
|
|
30
|
-
```
|
|
31
|
-
or
|
|
32
|
-
```bash
|
|
33
|
-
git checkout -b fix/my-bug-fix
|
|
34
|
-
```
|
|
35
|
-
6. Make Your Changes
|
|
36
|
-
Make your changes in the codebase. Ensure your code adheres to the project's coding standards and style guide.
|
|
37
|
-
7. Test Your Changes
|
|
38
|
-
Run the tests to ensure everything works as expected:
|
|
39
|
-
```bash
|
|
40
|
-
npm test
|
|
41
|
-
```
|
|
42
|
-
Add new tests if you’re introducing new functionality.
|
|
43
|
-
8. Commit Your Changes
|
|
44
|
-
Commit your changes with a clear and descriptive commit message:
|
|
45
|
-
```bash
|
|
46
|
-
git commit -m "Add new feature: [describe the feature]"
|
|
47
|
-
```
|
|
48
|
-
or for bug fixes:
|
|
49
|
-
```bash
|
|
50
|
-
git commit -m "Fix: [describe the bug fix]"
|
|
51
|
-
```
|
|
52
|
-
9. Push to Your Fork
|
|
53
|
-
Push your changes to your forked repository:
|
|
54
|
-
```bash
|
|
55
|
-
git push origin feature/my-new-feature
|
|
56
|
-
```
|
|
57
|
-
10. Create a Pull Request
|
|
58
|
-
1. Go to the original repository where you want to submit your changes.
|
|
59
|
-
2. Click on the "New Pull Request" button.
|
|
60
|
-
3. Select your branch from the dropdown and submit the pull request.
|
|
61
|
-
4. Provide a clear description of the changes you made and why they are needed.
|
|
62
|
-
|
|
63
|
-
#### Code of Conduct
|
|
64
|
-
|
|
65
|
-
By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). We expect everyone to be respectful and considerate in their interactions.
|
|
66
|
-
|
|
67
|
-
#### Additional Notes
|
|
68
|
-
|
|
69
|
-
- Issues: If you encounter any issues or have feature requests, please open an issue in the repository.
|
|
70
|
-
- Documentation: Ensure to update the documentation for any new features or changes you introduce.
|
|
71
|
-
- Formatting: Use a linter (like ESLint) to maintain code quality. Run `npm run lint` to check your code.
|
|
72
|
-
|
|
73
|
-
#### Thank You!
|
|
74
|
-
|
|
75
|
-
Your contributions help make @irfanshadikrishad/anilist a better tool for everyone. We appreciate your time and effort in making this project great!
|