klaim 1.2.28 → 1.2.30

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.
@@ -0,0 +1,38 @@
1
+ ---
2
+ name: Bug report
3
+ about: Create a report to help us improve
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Describe the bug**
11
+ A clear and concise description of what the bug is.
12
+
13
+ **To Reproduce**
14
+ Steps to reproduce the behavior:
15
+ 1. Go to '...'
16
+ 2. Click on '....'
17
+ 3. Scroll down to '....'
18
+ 4. See error
19
+
20
+ **Expected behavior**
21
+ A clear and concise description of what you expected to happen.
22
+
23
+ **Screenshots**
24
+ If applicable, add screenshots to help explain your problem.
25
+
26
+ **Desktop (please complete the following information):**
27
+ - OS: [e.g. iOS]
28
+ - Browser [e.g. chrome, safari]
29
+ - Version [e.g. 22]
30
+
31
+ **Smartphone (please complete the following information):**
32
+ - Device: [e.g. iPhone6]
33
+ - OS: [e.g. iOS8.1]
34
+ - Browser [e.g. stock browser, safari]
35
+ - Version [e.g. 22]
36
+
37
+ **Additional context**
38
+ Add any other context about the problem here.
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: Feature request
3
+ about: Suggest an idea for this project
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Is your feature request related to a problem? Please describe.**
11
+ A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12
+
13
+ **Describe the solution you'd like**
14
+ A clear and concise description of what you want to happen.
15
+
16
+ **Describe alternatives you've considered**
17
+ A clear and concise description of any alternative solutions or features you've considered.
18
+
19
+ **Additional context**
20
+ Add any other context or screenshots about the feature request here.
@@ -0,0 +1,128 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ We as members, contributors, and leaders 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, 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 a positive environment for our
18
+ community include:
19
+
20
+ * Demonstrating empathy and kindness toward other people
21
+ * Being respectful of differing opinions, viewpoints, and experiences
22
+ * Giving and gracefully accepting constructive feedback
23
+ * Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ * Focusing on what is best not just for us as individuals, but for the
26
+ overall community
27
+
28
+ Examples of unacceptable behavior include:
29
+
30
+ * The use of sexualized language or imagery, and sexual attention or
31
+ advances of any kind
32
+ * Trolling, insulting or derogatory comments, and personal or political attacks
33
+ * Public or private harassment
34
+ * Publishing others' private information, such as a physical or email
35
+ address, without their explicit permission
36
+ * Other conduct which could reasonably be considered inappropriate in a
37
+ professional setting
38
+
39
+ ## Enforcement Responsibilities
40
+
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
45
+
46
+ Community leaders have the right and responsibility to remove, edit, or reject
47
+ comments, commits, code, wiki edits, issues, and other contributions that are
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
50
+
51
+ ## Scope
52
+
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official e-mail address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
58
+
59
+ ## Enforcement
60
+
61
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
+ reported to the community leaders responsible for enforcement at
63
+ antho.eclips@gmail.com.
64
+ All complaints will be reviewed and investigated promptly and fairly.
65
+
66
+ All community leaders are obligated to respect the privacy and security of the
67
+ reporter of any incident.
68
+
69
+ ## Enforcement Guidelines
70
+
71
+ Community leaders will follow these Community Impact Guidelines in determining
72
+ the consequences for any action they deem in violation of this Code of Conduct:
73
+
74
+ ### 1. Correction
75
+
76
+ **Community Impact**: Use of inappropriate language or other behavior deemed
77
+ unprofessional or unwelcome in the community.
78
+
79
+ **Consequence**: A private, written warning from community leaders, providing
80
+ clarity around the nature of the violation and an explanation of why the
81
+ behavior was inappropriate. A public apology may be requested.
82
+
83
+ ### 2. Warning
84
+
85
+ **Community Impact**: A violation through a single incident or series
86
+ of actions.
87
+
88
+ **Consequence**: A warning with consequences for continued behavior. No
89
+ interaction with the people involved, including unsolicited interaction with
90
+ those enforcing the Code of Conduct, for a specified period of time. This
91
+ includes avoiding interactions in community spaces as well as external channels
92
+ like social media. Violating these terms may lead to a temporary or
93
+ permanent ban.
94
+
95
+ ### 3. Temporary Ban
96
+
97
+ **Community Impact**: A serious violation of community standards, including
98
+ sustained inappropriate behavior.
99
+
100
+ **Consequence**: A temporary ban from any sort of interaction or public
101
+ communication with the community for a specified period of time. No public or
102
+ private interaction with the people involved, including unsolicited interaction
103
+ with those enforcing the Code of Conduct, is allowed during this period.
104
+ Violating these terms may lead to a permanent ban.
105
+
106
+ ### 4. Permanent Ban
107
+
108
+ **Community Impact**: Demonstrating a pattern of violation of community
109
+ standards, including sustained inappropriate behavior, harassment of an
110
+ individual, or aggression toward or disparagement of classes of individuals.
111
+
112
+ **Consequence**: A permanent ban from any sort of public interaction within
113
+ the community.
114
+
115
+ ## Attribution
116
+
117
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118
+ version 2.0, available at
119
+ https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120
+
121
+ Community Impact Guidelines were inspired by [Mozilla's code of conduct
122
+ enforcement ladder](https://github.com/mozilla/diversity).
123
+
124
+ [homepage]: https://www.contributor-covenant.org
125
+
126
+ For answers to common questions about this code of conduct, see the FAQ at
127
+ https://www.contributor-covenant.org/faq. Translations are available at
128
+ https://www.contributor-covenant.org/translations.
@@ -0,0 +1,28 @@
1
+ # Contributing to Klaim
2
+
3
+ Thank you for your interest in contributing to Klaim! We welcome contributions from everyone. By participating in this project, you agree to abide by our Code of Conduct.
4
+
5
+ ## How Can I Contribute?
6
+
7
+ ### Reporting Bugs
8
+
9
+ If you find a bug, please open an issue describing the problem, steps to reproduce it, and any relevant information such as your environment and version.
10
+
11
+ ### Suggesting Enhancements
12
+
13
+ If you have an idea for a new feature or improvement, please open an issue to discuss it before submitting a pull request. This helps us coordinate efforts and ensure the feature aligns with the project's goals.
14
+
15
+ ### Pull Requests
16
+
17
+ 1. Fork the repository and create your branch from `main`.
18
+ 2. If you've added code, make sure it is covered by tests.
19
+ 3. Ensure the test suite passes.
20
+ 4. Submit your pull request, linking to the issue it addresses.
21
+
22
+ ## Code Style
23
+
24
+ Please adhere to the coding standards used in the project. This includes following the existing style and using TypeScript for type definitions.
25
+
26
+ ## Commit Messages
27
+
28
+ Write clear and concise commit messages. Follow the convention:
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2024 Anthony Bellancourt
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.
package/README.md CHANGED
@@ -3,11 +3,18 @@
3
3
  Klaim is a lightweight TypeScript library designed to manage APIs and record requests, optimized for an optimal user
4
4
  experience.
5
5
 
6
- ## Links
7
-
8
- - [NPM](https://www.npmjs.com/package/klaim)
9
- - [JSR](https://jsr.io/@antharuu/klaim)
10
- - [GitHub](https://github.com/antharuu/klaim)
6
+ ## 📚 Table of Contents
7
+
8
+ - [Features](#-features)
9
+ - [Installation](#-installation)
10
+ - [Usage](#-usage)
11
+ - [Basic API Configuration](#basic-api-configuration)
12
+ - [Route Definition](#route-definition)
13
+ - [Request Handling](#request-handling)
14
+ - [Hook Subscription](#hook-subscription)
15
+ - [Links](#-links)
16
+ - [Contributing](#-contributing)
17
+ - [License](#-license)
11
18
 
12
19
  ## 🚀 Features
13
20
 
@@ -36,11 +43,11 @@ deno add @antharuu/klaim
36
43
 
37
44
  ## 🛠 Usage
38
45
 
39
- Here’s a basic example to get you started:
46
+ ### Basic API Configuration
40
47
 
41
48
  ```typescript
42
49
  import {Api, Klaim, Route, Hook} from 'klaim';
43
- // For deno: import {Api, Klaim, Route, Hook} from "@antharuu/klaim";
50
+ // For deno: import { Api, Klaim, Route, Hook } from "@antharuu/klaim";
44
51
 
45
52
  // Your simple Todo type
46
53
  type Todo = {
@@ -50,47 +57,72 @@ type Todo = {
50
57
  completed: boolean;
51
58
  }
52
59
 
53
- // --- Basic API configuration
54
60
  // Create a new API with the name "hello" and the base URL "https://jsonplaceholder.typicode.com/"
55
- Api.create("hello", "https://jsonplaceholder.typicode.com/", () => {
56
- // Define routes for the API
57
- Route.get<Todo[]>("listTodos", "todos");
58
-
59
- // You can also define routes with parameters
60
- Route.get<Todo>("getTodo", "todos/[id]");
61
-
62
- // You can also define routes in post, (put, delete, etc)
63
- Route.post<Todo>("addTodo", "todos");
64
-
65
- // With before middleware
66
- Route.get<Todo>("getRandomTodo", "todos")
67
- .before(({url}) => {
68
- const random = Math.floor(Math.random() * 10) + 1;
69
- return ({url: `${url}/${random}`});
70
- });
71
-
72
- // With after middleware
73
- Route.get<Todo>("getFirstTodo", "todos")
74
- .after(({data: [first]}) => ({data: first}));
75
- });
61
+ Api.create("hello", "https://jsonplaceholder.typicode.com/");
62
+ ```
63
+
64
+ ### Route Definition
65
+
66
+ Define routes for the API:
67
+
68
+ ```typescript
69
+ // Define a route to get a list of todos
70
+ Route.get<Todo[]>("listTodos", "todos");
71
+
72
+ // Define a route to get a todo by id
73
+ Route.get<Todo>("getTodo", "todos/[id]");
74
+
75
+ // Define a route to add a new todo
76
+ Route.post<Todo>("addTodo", "todos");
77
+
78
+ // Define a route with before middleware
79
+ Route.get<Todo>("getRandomTodo", "todos")
80
+ .before(({url}) => {
81
+ const random = Math.floor(Math.random() * 10) + 1;
82
+ return ({url: `${url}/${random}`});
83
+ });
84
+
85
+ // Define a route with after middleware
86
+ Route.get<Todo>("getFirstTodo", "todos")
87
+ .after(({data: [first]}) => ({data: first}));
88
+ ```
76
89
 
77
- // --- Usage
90
+ ### Request Handling
91
+
92
+ Make requests using the defined routes:
93
+
94
+ ```typescript
78
95
  // Make a request to the "listTodos" route
79
- const listOfTodos = await Klaim.hello.todo<Todo>({id: 1})
96
+ const listOfTodos = await Klaim.hello.todo<Todo>({id: 1});
80
97
 
81
98
  // Make a request to the "getTodo" route with the parameter "id"
82
- const todo = await Klaim.hello.getTodo<Todo>({id: 1})
99
+ const todo = await Klaim.hello.getTodo<Todo>({id: 1});
83
100
 
84
101
  // Make a request to the "addTodo" route
85
- const newTodo = await Klaim.hello.addTodo<Todo>({}, {title: "New Todo", completed: false, userId: 1})
102
+ const newTodo = await Klaim.hello.addTodo<Todo>({}, {title: "New Todo", completed: false, userId: 1});
103
+ ```
86
104
 
87
- // You can subscribe to hooks from everywhere
88
- // Every time hello.getFirstTodo is called, the hook will be triggered
105
+ ### Hook Subscription
106
+
107
+ Subscribe to hooks to monitor specific events:
108
+
109
+ ```typescript
110
+ // Subscribe to the "hello.getFirstTodo" hook
89
111
  Hook.subscribe("hello.getFirstTodo", ({url}) => {
90
112
  console.log(`Requesting ${url}`);
91
113
  });
92
114
  ```
93
115
 
116
+ ## 🔗 Links
117
+
118
+ - [NPM](https://www.npmjs.com/package/klaim)
119
+ - [JSR](https://jsr.io/@antharuu/klaim)
120
+ - [GitHub](https://github.com/antharuu/klaim)
121
+
94
122
  ## 🤝 Contributing
95
123
 
96
- Contributions are welcome!
124
+ Contributions are welcome! Please see the [Contributing Guide](CONTRIBUTING.md) for more details.
125
+
126
+ ## 📜 License
127
+
128
+ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
package/SECURITY.md ADDED
@@ -0,0 +1,24 @@
1
+ # Security Policy
2
+
3
+ ## Supported Versions
4
+
5
+ We release updates and fixes regularly. We recommend using the latest version of Klaim to ensure you have the latest
6
+ security patches.
7
+
8
+ | Version | Supported |
9
+ |---------|--------------------|
10
+ | 1.x | :white_check_mark: |
11
+
12
+ ## Reporting a Vulnerability
13
+
14
+ If you find a security vulnerability, please report it to us via email
15
+ at [antho.eclips@gmail.com](mailto:antho.eclips@gmail.com). Do not open an issue on
16
+ GitHub, as this might reveal the vulnerability publicly.
17
+
18
+ Please include the following details in your report:
19
+
20
+ - A description of the vulnerability
21
+ - Steps to reproduce the vulnerability
22
+ - Any relevant information such as your environment and version
23
+
24
+ We will respond to your report as soon as possible and work with you to resolve the issue.
package/deno.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@antharuu/klaim",
3
- "version": "1.2.28",
3
+ "version": "1.2.30",
4
4
  "description": "Klaim is a lightweight TypeScript library designed to manage APIs and record requests, optimized for an optimal user experience.",
5
5
  "repository": {
6
6
  "type": "git",
package/package.json CHANGED
@@ -20,7 +20,7 @@
20
20
  },
21
21
  "homepage": "https://github.com/antharuu/klaim#readme",
22
22
  "type": "module",
23
- "version": "1.2.28",
23
+ "version": "1.2.30",
24
24
  "main": "dist/klaim.cjs.js",
25
25
  "module": "dist/klaim.es.js",
26
26
  "types": "dist/index.d.ts",
@@ -3,7 +3,7 @@ require('./load-env.cjs');
3
3
 
4
4
  module.exports = {
5
5
  github: {
6
- release: false,
6
+ release: true,
7
7
  },
8
8
  npm: {
9
9
  publish: false,