Skip to content

Commit 1c093ef

Browse files
Xeyos88Xeyos88
committed
Merge branch 'release/3.3.0'
2 parents 1132dd5 + f9c3a6b commit 1c093ef

35 files changed

+2127
-569
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md

+55
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
title: "[BUG] "
5+
labels: "bug"
6+
assignees: ""
7+
---
8+
9+
## Bug Description
10+
11+
A clear and concise description of what the bug is.
12+
13+
## Reproduction Steps
14+
15+
Steps to reproduce the behavior:
16+
17+
1. Go to '...'
18+
2. Click on '....'
19+
3. Scroll down to '....'
20+
4. See error
21+
22+
## Expected Behavior
23+
24+
A clear and concise description of what you expected to happen.
25+
26+
## Screenshots
27+
28+
If applicable, add screenshots to help explain your problem.
29+
30+
## Environment
31+
32+
- OS: [e.g. Windows 10, macOS Big Sur]
33+
- Browser: [e.g. Chrome 91, Safari 14]
34+
- Vue Version: [e.g. 3.2.0]
35+
- HY Vue Gantt Version: [e.g. 1.0.0]
36+
37+
## Console Errors
38+
39+
Please paste any error messages from the browser console:
40+
41+
```
42+
Paste errors here
43+
```
44+
45+
## Reproduction Repository or CodeSandbox
46+
47+
If possible, please provide a link to a minimal reproduction of the issue (e.g., a GitHub repository or CodeSandbox)
48+
49+
## Additional Context
50+
51+
Add any other context about the problem here. For example:
52+
53+
- Does it happen consistently or intermittently?
54+
- Are there any specific conditions that trigger it?
55+
- Have you tried any workarounds?

‎.github/ISSUE_TEMPLATE/config.yml

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Hyper Vue Gantt Discussions
4+
url: https://github.com/Xeyos88/HyVueGantt/discussions
5+
about: Please ask and answer questions here.
6+
- name: Hyper Vue Gantt Documentation
7+
url: https://xeyos88.github.io/HyVueGantt/
8+
about: Check the documentation for helpful information.

‎.github/ISSUE_TEMPLATE/documentation_request.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Documentation Request
3+
about: Request improvements or additions to documentation
4+
title: "[DOCS] "
5+
labels: "documentation"
6+
assignees: ""
7+
---
8+
9+
## Documentation Area
10+
11+
Describe which part of the documentation needs improvement:
12+
13+
- [ ] README
14+
- [ ] API Reference
15+
- [ ] Examples/Demos
16+
- [ ] Tutorial/Guide
17+
- [ ] TypeScript Typings
18+
- [ ] Code Comments
19+
- [ ] Other (please specify)
20+
21+
## Current Documentation
22+
23+
Please link to or describe the current documentation that needs improvement.
24+
25+
## Suggested Improvement
26+
27+
A clear and concise description of what should be added or how existing documentation should be improved.
28+
29+
## Why is this important?
30+
31+
Explain why this documentation improvement would be valuable.
32+
33+
## Would you be willing to contribute to the documentation?
34+
35+
- [ ] Yes, I'd be willing to write/improve this documentation
36+
- [ ] I might be able to help partially
37+
- [ ] No, I'm just suggesting the improvement

‎.github/ISSUE_TEMPLATE/feature_request.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
title: "[FEATURE] "
5+
labels: "enhancement"
6+
assignees: ""
7+
---
8+
9+
## Problem Statement
10+
11+
A clear and concise description of what problem this feature would solve. Ex. I'm always frustrated when [...]
12+
13+
## Proposed Solution
14+
15+
A clear and concise description of what you want to happen.
16+
17+
## Alternative Solutions
18+
19+
A clear and concise description of any alternative solutions or features you've considered.
20+
21+
## Example Use Cases
22+
23+
Describe how this feature would be used in practice and who would benefit from it.
24+
25+
```vue
26+
// If applicable, provide a code example of how this feature might be used
27+
<template>
28+
// Example of how your proposed feature might be configured
29+
<g-gantt-chart proposedFeature="..." />
30+
</template>
31+
```
32+
33+
## Additional Context
34+
35+
Add any other context, sketches, mockups, or references to similar implementations in other libraries that might help us understand your feature request.
36+
37+
## Would you be willing to contribute this feature?
38+
39+
- [ ] Yes, I'd be willing to implement this feature
40+
- [ ] I might be able to help partially
41+
- [ ] No, I'm just suggesting the idea

‎.github/ISSUE_TEMPLATE/question.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Question
3+
about: Ask a question about how to use HY Vue Gantt
4+
title: "[QUESTION] "
5+
labels: "question"
6+
assignees: ""
7+
---
8+
9+
## Question
10+
11+
A clear and concise description of your question.
12+
13+
## Use Case
14+
15+
What are you trying to accomplish? Context helps us provide more relevant answers.
16+
17+
## What I've Tried
18+
19+
Describe what you've already attempted to solve your problem:
20+
21+
```vue
22+
// Include code samples if relevant
23+
<template>
24+
<g-gantt-chart />
25+
</template>
26+
```
27+
28+
## Environment
29+
30+
- HY Vue Gantt Version: [e.g. 1.0.0]
31+
- Vue Version: [e.g. 3.2.0]
32+
- Browser: [e.g. Chrome, Safari]
33+
- OS: [e.g. Windows, macOS]
34+
35+
## Screenshots
36+
37+
If applicable, add screenshots to help explain your question.
38+
39+
## Additional Context
40+
41+
Add any other context about the question here.

‎.github/PULL_REQUEST_TEMPLATE.md

+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Pull Request
2+
3+
## Description
4+
5+
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
6+
7+
Fixes # (issue)
8+
9+
## Type of change
10+
11+
Please delete options that are not relevant.
12+
13+
- [ ] Bug fix (non-breaking change which fixes an issue)
14+
- [ ] New feature (non-breaking change which adds functionality)
15+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
16+
- [ ] Documentation update
17+
- [ ] Performance improvement
18+
- [ ] Code refactoring (no functional changes)
19+
- [ ] This change requires a documentation update
20+
21+
## How Has This Been Tested?
22+
23+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
24+
25+
- [ ] Test A (describe)
26+
- [ ] Test B (describe)
27+
28+
## Screenshots (if appropriate):
29+
30+
## Checklist:
31+
32+
Before submitting your PR, please review the following checklist:
33+
34+
- [ ] My code follows the style guidelines of this project
35+
- [ ] I have performed a self-review of my own code
36+
- [ ] I have commented my code, particularly in hard-to-understand areas
37+
- [ ] I have made corresponding changes to the documentation
38+
- [ ] My changes generate no new warnings
39+
- [ ] I have added tests that prove my fix is effective or that my feature works
40+
- [ ] New and existing unit tests pass locally with my changes
41+
- [ ] Any dependent changes have been merged and published in downstream modules
42+
43+
## Additional context
44+
45+
Add any other context about the pull request here.

‎.github/stale.yml

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Configuration for probot-stale - https://github.com/probot/stale
2+
3+
# Number of days of inactivity before an issue becomes stale
4+
daysUntilStale: 60
5+
# Number of days of inactivity before a stale issue is closed
6+
daysUntilClose: 21
7+
# Issues with these labels will never be considered stale
8+
exemptLabels:
9+
- pinned
10+
- security
11+
- bug
12+
- enhancement
13+
- "help wanted"
14+
- "in progress"
15+
# Label to use when marking an issue as stale
16+
staleLabel: stale
17+
# Comment to post when marking an issue as stale
18+
markComment: >
19+
This issue has been automatically marked as stale because it has not had
20+
recent activity. It will be closed if no further activity occurs. Thank you
21+
for your contributions.
22+
# Comment to post when closing a stale issue
23+
closeComment: >
24+
This issue has been automatically closed due to inactivity. Please feel free
25+
to reopen it if you still encounter this problem or need this feature.
26+
# Limit the number of actions per hour
27+
limitPerRun: 30
28+
# Only issues (not pull requests)
29+
only: issues

‎CHANGELOG.md

+2-9
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,13 @@ All notable changes to this project will be documented in this file.
44

55
---
66

7-
## [v3.2.0](https://github.com/Xeyos88/HyVueGantt/tree/v3.2.0) (2025-02-24)
7+
## [v3.1.2](https://github.com/Xeyos88/HyVueGantt/tree/v3.1.2) (2025-02-24)
88

9-
[Full Changelog](https://github.com/Xeyos88/HyVueGantt/compare/v3.1.0...v3.2.0)
10-
11-
12-
13-
**✨ New Features:**
14-
15-
- Release fix
9+
[Full Changelog](https://github.com/Xeyos88/HyVueGantt/compare/v3.1.1...v3.1.2)
1610

1711
**🐛 Fix:**
1812

1913
- Creation connection with group bars
20-
- Interaction with progress with active connection drawing
2114

2215
## [v3.1.1](https://github.com/Xeyos88/HyVueGantt/tree/v3.1.1) (2025-02-17)
2316

0 commit comments

Comments
 (0)