Skip to content

Commit 81f7db9

Browse files
Merge pull request #124 from OthmanImam/feat/Alias
Feat Update and Enhancement
2 parents 31fe195 + bd80c77 commit 81f7db9

8 files changed

Lines changed: 676 additions & 0 deletions

File tree

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug to help us improve
4+
labels: bug, needs-triage
5+
title: "[Bug]: "
6+
---
7+
8+
## Bug Report
9+
10+
### Describe the Bug
11+
A clear and concise description of what the bug is.
12+
13+
### Steps 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+
### Actual Behavior
24+
What actually happened. Include error messages and screenshots if applicable.
25+
26+
### Environment
27+
- OS: [e.g. Windows 11, macOS Ventura]
28+
- Node.js Version: [e.g. 20.10.0]
29+
- Version: [e.g. v0.1.0]
30+
- Browser (if applicable): [e.g. Chrome 120, Firefox 119]
31+
32+
### Additional Context
33+
Add any other context about the problem here. This could include:
34+
- Relevant logs
35+
- What you were trying to achieve
36+
- Any workarounds you've found
37+
---
38+
name: Bug Report
39+
about: Report a bug to help us improve
40+
labels: bug, needs-triage
41+
title: "[Bug]: "
42+
---
43+
44+
## Bug Report
45+
46+
### Describe the Bug
47+
A clear and concise description of what the bug is.
48+
49+
### Steps to Reproduce
50+
Steps to reproduce the behavior:
51+
1. Go to '...'
52+
2. Click on '....'
53+
3. Scroll down to '....'
54+
4. See error
55+
56+
### Expected Behavior
57+
A clear and concise description of what you expected to happen.
58+
59+
### Actual Behavior
60+
What actually happened. Include error messages and screenshots if applicable.
61+
62+
### Environment
63+
- OS: [e.g. Windows 11, macOS Ventura]
64+
- Node.js Version: [e.g. 20.10.0]
65+
- Version: [e.g. v0.1.0]
66+
- Browser (if applicable): [e.g. Chrome 120, Firefox 119]
67+
68+
### Additional Context
69+
Add any other context about the problem here. This could include:
70+
- Relevant logs
71+
- What you were trying to achieve
72+
- Any workarounds you've found
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: Feature Request
3+
about: Suggest a new feature or improvement
4+
labels: enhancement, needs-triage
5+
title: "[Feature]: "
6+
---
7+
8+
## Feature Request
9+
10+
### Problem Statement
11+
Describe the problem this feature would solve. What is currently missing or frustrating?
12+
13+
### Proposed Solution
14+
Describe the solution you'd like. Be as specific as possible about how this feature would work.
15+
16+
### Alternatives Considered
17+
Describe any alternative solutions or features you've considered and why you believe your proposed solution is better.
18+
19+
### Additional Context
20+
Add any other context, screenshots, or examples about the feature request here.
21+
22+
### Implementation Ideas (Optional)
23+
If you have ideas about how to implement this, share them here. This helps the maintainers understand the complexity.
24+
25+
### Would you be willing to contribute?
26+
- [ ] Yes, I'd like to submit a PR for this feature
27+
- [ ] I can help with testing
28+
- [ ] I can help with documentation
29+
- [ ] I'd rather let someone else work on this
30+
---
31+
name: Feature Request
32+
about: Suggest a new feature or improvement
33+
labels: enhancement, needs-triage
34+
title: "[Feature]: "
35+
---
36+
37+
## Feature Request
38+
39+
### Problem Statement
40+
Describe the problem this feature would solve. What is currently missing or frustrating?
41+
42+
### Proposed Solution
43+
Describe the solution you'd like. Be as specific as possible about how this feature would work.
44+
45+
### Alternatives Considered
46+
Describe any alternative solutions or features you've considered and why you believe your proposed solution is better.
47+
48+
### Additional Context
49+
Add any other context, screenshots, or examples about the feature request here.
50+
51+
### Implementation Ideas (Optional)
52+
If you have ideas about how to implement this, share them here. This helps the maintainers understand the complexity.
53+
54+
### Would you be willing to contribute?
55+
- [ ] Yes, I'd like to submit a PR for this feature
56+
- [ ] I can help with testing
57+
- [ ] I can help with documentation
58+
- [ ] I'd rather let someone else work on this

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
## Description
2+
3+
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
4+
5+
Fixes #(issue number)
6+
7+
## Type of Change
8+
9+
- [ ] Bug fix (non-breaking change which fixes an issue)
10+
- [ ] New feature (non-breaking change which adds functionality)
11+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
- [ ] Documentation update
13+
- [ ] Performance improvement
14+
- [ ] Code refactoring (no functional changes)
15+
16+
## How Has This Been Tested?
17+
18+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
19+
20+
- [ ] Unit tests added/updated
21+
- [ ] E2E tests added/updated
22+
- [ ] Manual testing performed
23+
- [ ] Tested in staging environment
24+
25+
## Checklist:
26+
27+
- [ ] My code follows the style guidelines of this project
28+
- [ ] I have performed a self-review of my code
29+
- [ ] I have commented my code, particularly in hard-to-understand areas
30+
- [ ] I have made corresponding changes to the documentation
31+
- [ ] My changes generate no new warnings
32+
- [ ] I have added tests that prove my fix is effective or that my feature works
33+
- [ ] New and existing unit tests pass locally with my changes
34+
- [ ] Any dependent changes have been merged and published in downstream modules
35+
36+
## Screenshots (if applicable)
37+
38+
If applicable, add screenshots to help explain your changes.
39+
40+
## Additional Notes
41+
42+
Add any other information that's important for reviewers to understand this PR.

CHANGELOG.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7+
8+
## [Unreleased]
9+
10+
### Added
11+
- Comprehensive documentation for portfolio optimization
12+
- WebSocket reconnection service with exponential backoff
13+
- Connection pool management for dashboard WebSockets
14+
- Event buffering to prevent WebSocket flooding
15+
- Multi-wallet management system
16+
- KYC guard with comprehensive coverage scanning
17+
- Rate limiting for sensitive endpoints
18+
- Token blacklisting service for secure session management
19+
- OpenTelemetry distributed tracing integration
20+
- Sentry error tracking and performance monitoring
21+
- Prometheus metrics with Grafana dashboards
22+
- Kubernetes health probes and liveness/readiness checks
23+
24+
### Security
25+
- Added helmet security headers
26+
- Implemented CORS whitelisting
27+
- Added input sanitization on all endpoints
28+
- Enhanced password hashing with bcrypt
29+
- JWT token with secure expiration
30+
31+
### Fixed
32+
- TypeScript compilation errors across all modules
33+
- Memory leaks in WebSocket connections
34+
- Race conditions in oracle submission batching
35+
- SQL injection vulnerabilities in query builders
36+
37+
## [0.1.0] - 2026-07-31
38+
39+
### Added
40+
- Initial NestJS project structure
41+
- Basic authentication system
42+
- Blockchain oracle module
43+
- DeFi portfolio tracking
44+
- Real-time dashboard WebSocket gateway
45+
- Core user profile management
46+
- Basic AI compute bridge
47+
48+
[Unreleased]: https://github.com/alian-structure/alian-structure-api/compare/v0.1.0...HEAD
49+
[0.1.0]: https://github.com/alian-structure/alian-structure-api/releases/tag/v0.1.0

CODE_OF_CONDUCT.md

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

0 commit comments

Comments
 (0)