Skip to content

Commit bf662f4

Browse files
Update issue templates
1 parent c23675d commit bf662f4

File tree

2 files changed

+102
-0
lines changed

2 files changed

+102
-0
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
# Bug Report
11+
12+
## Summary
13+
14+
**Describe the bug in one concise sentence**
15+
A clear and brief description of what the unexpected behavior is.
16+
17+
## Version
18+
19+
- **@rbac/rbac version:**
20+
(e.g., `2.1.1`)
21+
22+
- **Environment:**
23+
(e.g., Browser, Node.js version, Deno, Bun, Cloudflare Workers)
24+
25+
## Reproduction Steps
26+
27+
Steps to reliably reproduce the issue:
28+
29+
1. Go to …
30+
2. Run …
31+
3. Call …
32+
4. Observe …
33+
34+
## Expected Behavior
35+
36+
Describe what you expected to happen instead of the bug.
37+
38+
Example:
39+
The role check should return `true` for user with `admin` role when permission is defined as allowed.
40+
41+
## Actual Behavior
42+
43+
Describe what actually happened.
44+
45+
Example:
46+
The role check returns `false` despite correct role and permission.
47+
48+
## Minimal Reproduction
49+
50+
Provide a minimal code snippet that reproduces the issue:
51+
52+
```js
53+
import { RBAC } from '@rbac/rbac';
54+
55+
const rbac = new RBAC({ rules: [...] });
56+
57+
const result = rbac.can('admin', 'some:action');
58+
59+
console.log(result);
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
# Feature Request Template
11+
12+
Use this template when proposing a new feature or enhancement for this project. Before submitting, please search existing issues to avoid duplicates. :contentReference[oaicite:0]{index=0}
13+
14+
---
15+
16+
## Summary
17+
18+
**What is the feature you are requesting?**
19+
Provide a concise title and a short description of the proposed feature.
20+
21+
## Motivation
22+
23+
**Why should this feature be added?**
24+
Explain the problem this feature will solve or the benefit it introduces. Provide context and use cases.
25+
26+
## Proposed Solution
27+
28+
**Describe your idea for how this feature should work.**
29+
Include example code, API surface, configuration options, or UX considerations if applicable.
30+
31+
## Alternatives Considered
32+
33+
**Have you explored other ways to solve this problem?**
34+
List any alternative approaches and why they were rejected.
35+
36+
## Impact
37+
38+
**What areas of the project would this feature affect?**
39+
(e.g., core API, performance, UI behavior, runtime compatibility).
40+
41+
## Additional Context
42+
43+
Provide any additional information that might help implementation (links, design docs, related issues, user stories).

0 commit comments

Comments
 (0)