FinceptTerminal is a modern finance application offering advanced market analytics, investment research, and economic data tools, designed for interactive exploration and data-driven decision-making in a user-friendly environment.
C++ ai-agentsalgorithmic-tradingbloomberg-terminalcppfinancefinancial-marketsfintechgood-first-issueinvestmentinvestment-researchmachine-learningopensourcepythonqtquantitative-financestock-markettrading
data sources added
tilakpatel22cb2d1fa002b4
diff --git a/.dockerignore b/.dockerignoreindex 5972ecfe1..2a8c597c2 100644--- a/.dockerignore+++ b/.dockerignore@@ -46,5 +46,7 @@ te/finscript/upx.exesetup.py+FinceptTerminal.exe+launcher.cppdiff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.mdnew file mode 100644index 000000000..d89a4102c--- /dev/null+++ b/.github/ISSUE_TEMPLATE/bug_report.md@@ -0,0 +1,121 @@+---+name: 🐛 Bug Report+about: Report a bug or unexpected behavior in Fincept Terminal+title: "[BUG] "+labels: "type:bug, status:triage"+assignees: ""+---++## Preliminary Checks+<!-- Please confirm you've done the following by checking the boxes -->+- [ ] I have searched existing issues to ensure this bug hasn't been reported before+- [ ] I have tried the latest version of the application+- [ ] I have read the troubleshooting documentation++## Bug Information++### Bug Severity+<!-- Select the severity level -->+- [ ] Low - Minor issue, doesn't affect core functionality+- [ ] Medium - Affects functionality but workaround exists+- [ ] High - Significantly impacts functionality, no workaround+- [ ] Critical - Application crashes or data loss++### Bug Category+<!-- Select the affected area -->+- [ ] User Interface+- [ ] Data Processing+- [ ] Performance+- [ ] Installation/Setup+- [ ] Authentication+- [ ] API/Integration+- [ ] Documentation+- [ ] Other: ___________++## 🐛 Bug Description+<!-- A clear and concise description of what the bug is -->+++## 🔄 Steps to Reproduce+<!-- Exact steps to reproduce the behavior -->+1. Go to '...'+2. Click on '...'+3. Scroll down to '...'+4. See error++**Reproduction Rate:**+- [ ] Always (100%)+- [ ] Often (75-99%)+- [ ] Sometimes (25-74%)+- [ ] Rarely (1-24%)+- [ ] Unable to reproduce++## ✅ Expected Behavior+<!-- What you expected to happen -->+++## ❌ Actual Behavior+<!-- What actually happened -->+++## 📋 Error Messages/Logs+<!-- Any error messages, stack traces, or relevant log output -->+```+Paste any error messages or logs here...+```++**Console Output:**+```+Paste console output here if applicable...+```++## 🖥️ Environment Information+<!-- Information about your environment -->+- **OS:** [e.g. Ubuntu 20.04, macOS 13.0, Windows 11]+- **Python Version:** [e.g. 3.11.0]+- **Fincept Terminal Version:** [e.g. 1.2.3]+- **Docker Version:** [e.g. 20.10.17]+- **Browser (if applicable):** [e.g. Chrome 108.0.5359.71]+- **Terminal/Shell:** [e.g. bash, zsh, PowerShell]++## 📚 Additional Context+<!-- Any other context about the problem -->++**When did this start happening?**+++**Does it happen consistently or intermittently?**+++**Any recent changes to your setup?**+++**Screenshots or screen recordings:**+<!-- Drag and drop files here -->+++**Related issues or discussions:**+++## 🔄 Workarounds+<!-- Any temporary workarounds you've found -->+++## 🧪 Testing+<!-- Would you be willing to test a potential fix? -->+- [ ] Yes, I can test fixes+- [ ] Yes, with guidance+- [ ] Maybe, depending on complexity+- [ ] No, not available for testing++## 📊 Impact Assessment+<!-- How does this bug affect your usage? -->+- [ ] Blocks all functionality+- [ ] Blocks some critical functionality+- [ ] Reduces efficiency+- [ ] Minor inconvenience+- [ ] Cosmetic issue only++---++**Thank you for taking the time to report this bug! 🐛**\ No newline at end of filediff --git a/.github/ISSUE_TEMPLATE/documentation.md b/.github/ISSUE_TEMPLATE/documentation.mdnew file mode 100644index 000000000..8c3399d7f--- /dev/null+++ b/.github/ISSUE_TEMPLATE/documentation.md@@ -0,0 +1,215 @@+---+name: 📚 Documentation Issue+about: Report missing, unclear, or incorrect documentation+title: "[DOCS] "+labels: "type:documentation, status:triage"+assignees: ""+---++## Preliminary Checks+<!-- Please confirm you've done the following by checking the boxes -->+- [ ] I have searched existing documentation issues+- [ ] I have checked multiple documentation sources (README, wiki, etc.)+- [ ] I have looked for community discussions about this topic++## Documentation Issue Details++### Documentation Type+<!-- Select the type of documentation issue -->+- [ ] Missing documentation+- [ ] Incorrect/outdated information+- [ ] Unclear/confusing explanation+- [ ] Broken links or references+- [ ] Code examples don't work+- [ ] API documentation issues+- [ ] Installation/setup guide issues+- [ ] Tutorial/guide improvements+- [ ] Other: ___________++### Documentation Section+<!-- Which section of documentation is affected? -->+- [ ] README+- [ ] Installation Guide+- [ ] Quick Start/Getting Started+- [ ] API Reference+- [ ] Configuration Guide+- [ ] Tutorials/Examples+- [ ] Troubleshooting+- [ ] Contributing Guidelines+- [ ] Code Comments/Docstrings+- [ ] Other: ___________++### Urgency Level+<!-- How urgent is this documentation fix? -->+- [ ] Low - Nice to have improvement+- [ ] Medium - Important for user experience+- [ ] High - Blocking users from using features+- [ ] Critical - Causing widespread confusion/errors++## 📍 Documentation Location+<!-- Where is the documentation issue located? -->++**File/Page:** [e.g., README.md, docs/installation.md]++**Section/Heading:** [e.g., "Installation via Docker"]++**Line numbers:** [if applicable]++**URL:** [if online documentation]++**Direct link to problematic section:**+++## 📚 Issue Description+<!-- Describe the documentation problem in detail -->++**What exactly is wrong with the current documentation?**+++**What information is missing or unclear?**+++**What confusion does this cause?**+++## 👥 User Impact+<!-- How does this documentation issue affect users? -->++**Who is affected?**+- [ ] New users+- [ ] Experienced users+- [ ] Developers/Contributors+- [ ] System administrators+- [ ] API consumers+- [ ] All users++**What problems does this cause?**+++**How does this impact the user experience?**+++**Examples of user confusion or complaints:**+++## ✅ Expected Documentation+<!-- What should the documentation say or include? -->++**What information should be added?**+++**How should it be explained?**+++**What examples would be helpful?**+++**Suggested structure/organization:**+++## 🔄 Current Workaround+<!-- How are users currently finding this information? -->++**Alternative sources of information:**+++**Trial and error process users go through:**+++**Community discussions/forums addressing this:**+++## 💡 Suggested Improvement+<!-- Your specific suggestions for improving the documentation -->++**Specific text changes:**+++**Additional sections to add:**+++**Better examples or code snippets:**+```+// Example code here+```++**Improved organization/structure:**+++**Visual aids needed:**+- [ ] Diagrams+- [ ] Screenshots+- [ ] Flow charts+- [ ] Code snippets+- [ ] Video tutorials++## 📚 Additional Context+<!-- Any other relevant information -->++**Related documentation that works well:**+++**External resources that could be referenced:**+++**User feedback received:**+++**Screenshots of confusing sections:**+<!-- Drag and drop images here -->++**Standards or best practices to follow:**+++## 🤝 Contribution Willingness+<!-- Are you willing to help improve the documentation? -->+- [ ] Yes, I can write/update the documentation+- [ ] Yes, I can review proposed changes+- [ ] I can provide feedback on drafts+- [ ] I can help with proofreading+- [ ] I can help with technical accuracy review+- [ ] No, but I can provide more details if needed++**Contribution timeline:**+- [ ] Available immediately+- [ ] Available within a week+- [ ] Available within a month+- [ ] Available when convenient++## 📝 Content Suggestions+<!-- Draft content or outline for the improvement -->++**Proposed content outline:**+1.+2.+3.++**Draft text (if you have suggestions):**+++**Code examples to include:**+```+// Suggested code examples+```++## 🔍 Quality Standards+<!-- How should we ensure the documentation meets quality standards? -->++**Documentation should include:**+- [ ] Clear step-by-step instructions+- [ ] Working code examples+- [ ] Prerequisites clearly stated+- [ ] Expected outcomes described+- [ ] Troubleshooting section+- [ ] Links to related topics+- [ ] Version information++**Target audience considerations:**+- [ ] Beginner-friendly language+- [ ] Technical accuracy for developers+- [ ] Cross-platform compatibility notes+- [ ] Multiple usage scenarios++---++**Thank you for helping us improve Fincept Terminal's documentation! 📚**\ No newline at end of filediff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.mdindex 7e3469c44..fc0176d09 100644--- a/.github/ISSUE_TEMPLATE/feature_request.md+++ b/.github/ISSUE_TEMPLATE/feature_request.md@@ -1,47 +1,128 @@----name: Feature Request-about: Suggest a new feature or functionality for this project-title: "[FEATURE]"-labels: 'type:feature'-assignees: ''-+name: 🌟 Feature Request+about: Suggest a new feature or enhancement for Fincept Terminal+title: "[FEATURE] "+labels: "type:feature, status:triage"+assignees: ""---+## Preliminary Checks+<!-- Please confirm you've done the following by checking the boxes -->+- [ ] I have searched existing issues to ensure this feature hasn't been requested before+- [ ] I have checked the project roadmap/documentation+- [ ] I understand this is for requesting new functionality++## Feature Information++### Feature Category+<!-- Select the most appropriate category -->+- [ ] UI/UX Enhancement+- [ ] Performance Improvement+- [ ] New Functionality+- [ ] Integration/API+- [ ] Documentation+- [ ] Developer Experience+- [ ] Security+- [ ] Other: ___________++### Priority Level+<!-- Select the priority level -->+- [ ] Low - Nice to have+- [ ] Medium - Would improve workflow+- [ ] High - Significantly impacts productivity+- [ ] Critical - Blocking current work+## 🌟 Feature Description-Provide a clear and concise description of the feature you are requesting. Include any relevant context or background.+<!-- Provide a clear and detailed description of the feature -->-----## 🛠️ Use Case-Explain why this feature is important and how it would be used. Who will benefit from it, and what problem does it solve?+## 🛠️ Use Case & Problem Statement+<!-- Explain the problem this feature solves and who benefits from it -->----+**What problem does this solve?**-## 🎯 Expected Behavior-Describe how you expect the feature to work. Include details about its behavior, functionality, and any specific requirements.----+**Who will use this feature?**-## 📚 Additional Resources-Provide any resources, links, or references that could help in understanding or implementing the feature. Examples might include:-- Relevant documentation or articles-- Similar features in other projects-- Mockups or designs (if available)----+**How often would it be used?**+++**What's the impact of not having this feature?**+++## 🎯 Detailed Feature Specification+<!-- Describe exactly how you expect the feature to work -->++**Step-by-step workflow:**+1.+2.+3.++**User interactions:**+++**Expected outputs/results:**+++**Integration points:**+++**Configuration options:**+++## ✅ Acceptance Criteria+<!-- Define what "done" looks like for this feature -->+- [ ] User can perform action X+- [ ] System responds with Y+- [ ] Feature works on platforms A, B, C+- [ ] Documentation is updated+- [ ] Tests are included## 🔄 Alternatives Considered-(Optional) Share any alternative solutions you considered and explain why this proposed feature is the best approach.+<!-- What alternative solutions have you considered? -->----+**Alternative approach 1:**-## 📷 Visuals or Screenshots (Optional)-Attach any visuals, diagrams, or screenshots to illustrate your feature request.----+**Alternative approach 2:**+++**Why the proposed solution is better:**+++## 📚 Additional Context & Resources+<!-- Any additional information, links, or resources -->++**Links to relevant documentation:**+++**Examples from other projects:**+++**Research or articles:**+++**Dependencies or constraints:**+++**Technical specifications:**+++## 🤝 Implementation+<!-- Are you willing to help implement this feature? -->+- [ ] Yes, I can implement this feature+- [ ] Yes, I can help with implementation+- [ ] I can provide guidance/review+- [ ] I can help with testing+- [ ] No, but I can provide feedback-## 💡 Additional Context-Add any other relevant information about the feature request, such as constraints, dependencies, or potential challenges.+## 🖥️ Environment Information+<!-- Your current environment (if relevant) -->+- **OS:** [e.g. Ubuntu 20.04, macOS 13.0, Windows 11]+- **Python Version:** [e.g. 3.11.0]+- **Fincept Terminal Version:** [e.g. 1.2.3]+- **Docker Version:** [e.g. 20.10.17]---diff --git a/.github/ISSUE_TEMPLATE/improvement.md b/.github/ISSUE_TEMPLATE/improvement.mdindex 08d6f9fda..343c39675 100644--- a/.github/ISSUE_TEMPLATE/improvement.md+++ b/.github/ISSUE_TEMPLATE/improvement.md@@ -1,51 +1,254 @@----name: Improvement-about: Suggest enhancements or improvements for this project-title: "[IMPROVE]"-labels: 'type:enhancement'-assignees: ''-+name: ✨ Improvement Suggestion+about: Suggest enhancements or improvements to existing features in Fincept Terminal+title: "[IMPROVE] "+labels: "type:enhancement, status:triage"+assignees: ""----## 🌟 Feature to be Improved-A concise description of the feature or functionality that could be enhanced, along with relevant context. Why do you think this improvement is necessary?+## Preliminary Checks+<!-- Please confirm you've done the following by checking the boxes -->+- [ ] I have searched existing issues to ensure this improvement hasn't been suggested before+- [ ] I have checked the project roadmap and current development plans+- [ ] I understand this is for improving existing features (not adding new ones)----+## Improvement Details-## 🔄 Current vs Proposed-**Current Behavior:**-Briefly describe how the feature currently functions or behaves.+### Improvement Category+<!-- Select the type of improvement -->+- [ ] User Interface/Experience+- [ ] Performance Enhancement+- [ ] Code Quality/Refactoring+- [ ] Error Handling/Messaging+- [ ] Configuration/Settings+- [ ] Accessibility+- [ ] Developer Experience+- [ ] Testing/Quality Assurance+- [ ] Documentation Enhancement+- [ ] Security Improvement+- [ ] Other: ___________-**Proposed Behavior:**-Explain what changes or improvements you are suggesting and how it should behave after the enhancement.+### Impact Scope+<!-- Who would benefit from this improvement? -->+- [ ] End Users+- [ ] Developers/Contributors+- [ ] System Administrators+- [ ] All Users+- [ ] Specific User Group: ___________----+### Improvement Priority+<!-- How important is this improvement? -->+- [ ] Low - Minor enhancement, quality of life improvement+- [ ] Medium - Noticeable improvement to user experience+- [ ] High - Significant impact on usability or efficiency+- [ ] Critical - Addresses major pain points or blockers-## 🛠️ Suggested Implementation-If applicable, provide details on how this improvement can be implemented. Include potential steps, technologies, or methods.+## ✨ Feature/Area to be Improved+<!-- Clearly identify what existing feature or area needs improvement -->----+**Which specific feature, component, or area needs improvement?**-## ✅ Expected Outcomes-Describe the anticipated benefits or outcomes of this improvement. How will it impact the project, users, or overall functionality?----+**What version are you currently using?**-## 📚 Additional Resources-Provide any additional information, resources, or links that could help in implementing the suggested improvement. For example:-- Links to documentation or reference materials-- Examples or mockups (if available)----+**Why does this need improvement?**-## 🗳️ Alternatives Considered-(Optional) Describe any alternative approaches you thought about and why this particular suggestion is better.----+## 📋 Current Behavior+<!-- Describe how the feature currently works -->++**Current workflow or process:**+1.+2.+3.++**Current limitations or pain points:**+++**What makes it difficult or inefficient?**+++**User frustrations with current implementation:**+++## 🎯 Proposed Improvement+<!-- Describe your suggested enhancement in detail -->++**How should it work instead?**+++**What specific changes would you make?**+++**Improved workflow:**+1.+2.+3.++**Key benefits of the improvement:**+++## 👤 User Stories+<!-- Describe the improvement from a user's perspective -->++**Primary user story:**+As a [type of user], I want [improvement] so that [benefit/outcome].++**Additional scenarios:**+- As a _____, I want _____ so that _____+- As a _____, I want _____ so that _____++**Example use cases:**+++## ✅ Expected Outcomes & Benefits+<!-- What positive impacts would this improvement have? -->++**Improved user experience:**+++**Performance gains:**+++**Reduced errors/confusion:**+++**Time savings:**+++**Better accessibility:**+++**Easier maintenance:**+++**Other benefits:**+++## 📊 Success Metrics+<!-- How would you measure the success of this improvement? -->++**Quantifiable metrics:**+- [ ] Reduced time to complete task X by ___%+- [ ] Decreased error rates by ___%+- [ ] Improved user satisfaction scores+- [ ] Better performance benchmarks+- [ ] Reduced support requests by ___%++**Qualitative indicators:**+++## 🛠️ Suggested Implementation Approach+<!-- How do you think this improvement could be implemented? -->++**Technical approach or strategy:**+++**Potential tools/libraries to use:**+++**Step-by-step implementation plan:**+1.+2.+3.++**Considerations for backward compatibility:**+++**Required changes to existing code/config:**+++## 🔄 Alternatives Considered+<!-- What other approaches did you consider? -->++**Alternative approach 1:**+- Description:+- Pros:+- Cons:++**Alternative approach 2:**+- Description:+- Pros:+- Cons:++**Why your suggested approach is preferred:**+++## ⚠️ Potential Challenges/Drawbacks+<!-- What challenges or negative impacts might this improvement have? -->++**Potential issues:**+- [ ] Breaking changes or compatibility issues+- [ ] Performance trade-offs+- [ ] Increased complexity+- [ ] Learning curve for users+- [ ] Implementation difficulty+- [ ] Resource requirements++**Mitigation strategies:**+++## 📚 Additional Context & Resources+<!-- Any additional information, examples, or resources -->++**Links to similar implementations in other tools:**+++**User feedback or complaints about current behavior:**+++**Research or articles supporting the improvement:**+++**Screenshots or mockups of proposed changes:**+<!-- Drag and drop images here -->++**Relevant standards or best practices:**+++## 🤝 Implementation Contribution+<!-- Are you willing to help implement this improvement? -->+- [ ] Yes, I can implement this improvement myself+- [ ] Yes, I can help with implementation+- [ ] I can provide technical guidance/review+- [ ] I can help with testing and validation+- [ ] I can provide feedback on proposed solutions+- [ ] No, but I can provide detailed requirements++**Technical expertise:**+- [ ] Frontend development+- [ ] Backend development+- [ ] Database design+- [ ] UI/UX design+- [ ] Testing/QA+- [ ] Documentation+- [ ] Other: ___________++## 🖥️ Environment Information+<!-- Your current environment (if relevant to the improvement) -->+- **OS:** [e.g. Ubuntu 20.04, macOS 13.0, Windows 11]+- **Python Version:** [e.g. 3.11.0]+- **Fincept Terminal Version:** [e.g. 1.2.3]+- **Usage Context:** [e.g. local development, production deployment]++## ⏰ Timeline Preference+<!-- When would you like to see this improvement? -->+- [ ] Next patch release (urgent)+- [ ] Next minor release (1-2 months)+- [ ] Next major release (3-6 months)+- [ ] Future release (6+ months)+- [ ] No specific timeline++**Reasoning for timeline:**+-## 📷 Visuals or Screenshots (Optional)-Add any visuals, diagrams, or screenshots that help illustrate your proposed improvement.+## 🔗 Related Issues/Discussions+<!-- Link any related issues or discussions -->+- Related to #+- Mentioned in #+- Discussed in [forum/discussion link]----**Thank you for suggesting this improvement! We value your input. 🙌**\ No newline at end of file+**Thank you for helping us improve Fincept Terminal! ✨**\ No newline at end of filediff --git a/.github/ISSUE_TEMPLATE/performance_issues.md b/.github/ISSUE_TEMPLATE/performance_issues.mdnew file mode 100644index 000000000..7badc7e52--- /dev/null+++ b/.github/ISSUE_TEMPLATE/performance_issues.md@@ -0,0 +1,169 @@+---+name: ⚡ Performance Issue+about: Report performance problems, slowness, or resource usage issues+title: "[PERFORMANCE] "+labels: "type:performance, status:triage"+assignees: ""+---++## Preliminary Checks+<!-- Please confirm you've done the following by checking the boxes -->+- [ ] I have searched existing issues for similar performance problems+- [ ] I have verified this isn't caused by my system/network+- [ ] I have tried with minimal configuration/plugins++## Performance Issue Details++### Performance Issue Type+<!-- Select the type of performance issue -->+- [ ] Slow startup/initialization+- [ ] Slow data processing+- [ ] High memory usage+- [ ] High CPU usage+- [ ] Slow UI responsiveness+- [ ] Network/API delays+- [ ] Database query performance+- [ ] Memory leaks+- [ ] Other: ___________++### Impact Severity+<!-- How much does this impact your usage? -->+- [ ] Low - Slightly noticeable, doesn't affect workflow+- [ ] Medium - Noticeable delays, minor workflow impact+- [ ] High - Significant delays, major workflow impact+- [ ] Critical - Unusable, blocks all work++## ⚡ Performance Issue Description+<!-- Describe the performance problem in detail -->++**What specific operation or feature is slow?**+++**How long does it take vs. how long should it take?**+++## 📊 Performance Metrics+<!-- Provide specific performance measurements -->++| Metric | Current Performance | Expected Performance | Difference |+|--------|-------------------|---------------------|------------|+| **Operation Time** | ___ seconds/minutes | ___ seconds/minutes | ___% slower |+| **Memory Usage** | ___ MB/GB | ___ MB/GB | ___% higher |+| **CPU Usage** | ___% | ___% | ___% higher |+| **Data Size** | ___ records/MB | ___ records/MB | - |++**Frequency:** How often does this happen?+- [ ] Every time+- [ ] Most of the time (75-99%)+- [ ] Sometimes (25-74%)+- [ ] Rarely (1-24%)++## 🔄 Steps to Reproduce+<!-- Exact steps to reproduce the performance issue -->+1. Load dataset of size X+2. Perform operation Y+3. Observe slow performance+4. Measure timing/resource usage++## 🔍 Profiling Information+<!-- Any profiling data, benchmarks, or performance logs -->++**Tools used for measurement:**+- [ ] Built-in timing+- [ ] cProfile+- [ ] memory_profiler+- [ ] htop/top+- [ ] Browser DevTools+- [ ] Other: ___________++**Profiling Data:**+```+Paste profiling output, performance logs, or benchmark results here+```++**Screenshots of system monitors:**+<!-- Drag and drop images here -->++## 🖥️ Environment Information+<!-- Detailed system information -->++**System Specifications:**+- **OS:** [e.g. Ubuntu 20.04]+- **CPU:** [e.g. Intel i7-9700K, 8 cores]+- **RAM:** [e.g. 16GB]+- **Storage:** [e.g. SSD, HDD]+- **Python Version:** [e.g. 3.11.0]+- **Fincept Terminal Version:** [e.g. 1.2.3]++**Configuration:**+- **Docker:** [ ] Yes [ ] No (Version: _______)+- **Data source:** [e.g. local files, remote API, database]+- **Dataset size:** [e.g. 10k rows, 100MB file]+- **Concurrent users:** [e.g. 1, 10, 100]++## 📈 Performance Comparison+<!-- How does performance compare in different scenarios? -->++**Different data sizes:**+- Small dataset (___): ___+- Medium dataset (___): ___+- Large dataset (___): ___++**Different environments:**+- Local: ___+- Docker: ___+- Cloud: ___++**Previous versions:**+- Version X.X.X: ___+- Current version: ___++**Similar tools comparison:**+- Tool Y: ___+- Tool Z: ___++## 📚 Additional Context+<!-- Any other relevant information -->++**When did you first notice this performance issue?**+++**Has performance degraded over time?**+++**Any recent changes that might have caused this?**+++**Network conditions (if relevant):**+++**Other applications running:**+++## 🛠️ Potential Solutions+<!-- Any ideas for improving performance -->++**Suggestions:**+- [ ] Caching improvements+- [ ] Algorithm optimization+- [ ] Database indexing+- [ ] Parallel processing+- [ ] Memory optimization+- [ ] Other: ___________++## 🧪 Testing Availability+<!-- Can you help test performance improvements? -->+- [ ] Yes, I can run benchmarks and provide feedback+- [ ] Yes, but need guidance on testing+- [ ] Limited availability for testing+- [ ] No, not available for testing++**Testing commitment:**+- [ ] Can test within 24 hours+- [ ] Can test within a week+- [ ] Can test when convenient+- [ ] Cannot commit to testing timeline++---++**Thank you for helping us improve Fincept Terminal's performance! ⚡**\ No newline at end of filediff --git a/.github/ISSUE_TEMPLATE/report_bug.md b/.github/ISSUE_TEMPLATE/report_bug.mddeleted file mode 100644index 955db17d9..000000000--- a/.github/ISSUE_TEMPLATE/report_bug.md+++ /dev/null@@ -1,32 +0,0 @@-----name: Bug Report-about: Create a report to help us improve-title: "[Bug] <Short Description>"-labels: bug-assignees: ''-------### Describe the Bug-Provide a clear and concise description of what the bug is.--### Steps to Reproduce-Steps to reproduce the behavior:-1. Go to '...'-2. Click on '...'-3. Scroll down to '...'-4. See error--### Expected Behavior-A clear and concise description of what you expected to happen.--### Screenshots-If applicable, add screenshots to help explain your problem.--### System Information-- **OS**: [e.g., Windows, macOS, Linux]-- **Browser**: [e.g., Chrome, Safari, Firefox]-- **Version**: [e.g., 22]--### Additional Context-Add any other context about the problem here.\ No newline at end of filediff --git a/.github/PULL_REQUEST_TEMPLATE/pull_request_for_terminal.md b/.github/PULL_REQUEST_TEMPLATE/pull_request_for_terminal.mdindex d70b71c1d..f3207c1dd 100644--- a/.github/PULL_REQUEST_TEMPLATE/pull_request_for_terminal.md+++ b/.github/PULL_REQUEST_TEMPLATE/pull_request_for_terminal.md@@ -1,51 +1,230 @@+## 📝 Pull Request Summary++### Type of Change+<!-- Please select the type of change this PR introduces -->+- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)+- [ ] ✨ New feature (non-breaking change which adds functionality)+- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)+- [ ] 🔄 Refactoring (code change that neither fixes a bug nor adds a feature)+- [ ] 📚 Documentation update+- [ ] 🧪 Test addition/improvement+- [ ] ⚡ Performance improvement+- [ ] 🔧 Configuration/build changes+- [ ] 🎨 UI/UX improvements++### Description+<!-- Provide a clear and concise description of what this PR does -->+++### Motivation and Context+<!-- Why is this change required? What problem does it solve? -->+<!-- If it fixes an open issue, please link to the issue here -->++----name: Pull Request-about: Submit changes or additions to the Fincept Terminal project-title: "[PR]"-labels: ''-assignees: ''++## 🔗 Related Issues+<!-- Link related issues using keywords to auto-close them when merged -->+- Fixes #+- Closes #+- Addresses #+- Related to #----## 📝 Description-Provide a brief overview of the changes introduced in this pull request. What does this PR do? Highlight the purpose of the changes.+## 🔨 Technical Details++### Changes Made+<!-- List the specific technical changes made -->+- [ ] **Core Logic Changes:**+- [ ] **API Changes:**+- [ ] **Database Changes:**+- [ ] **UI/Frontend Changes:**+- [ ] **Configuration Changes:**+- [ ] **Dependencies Added/Updated:**+- [ ] **Documentation Updates:**++### Files Modified+<!-- List key files that were modified -->+- `file1.py` - Description of changes+- `file2.js` - Description of changes+- `config.yaml` - Description of changes----## 🔨 Changes Made-List the specific changes or additions made in this PR:-- [ ] Feature/Functionality added: *Describe the feature or functionality*-- [ ] Bug fixed: *Describe the bug and fix implemented*-- [ ] Code improvement/refactor: *Mention areas improved or refactored*-- [ ] Documentation update: *Mention updated/added docs*-- [ ] Test cases added/updated: *Mention test improvements*+## 🧪 Testing++### Testing Strategy+<!-- Describe how you tested these changes -->+- [ ] Unit tests added/updated+- [ ] Integration tests added/updated+- [ ] Manual testing performed+- [ ] End-to-end testing performed+- [ ] Performance testing conducted+- [ ] Cross-platform testing (if applicable)++### Test Coverage+<!-- If applicable, mention test coverage changes -->+- Current coverage: _%+- Coverage change: +/- _%++### Testing Instructions+<!-- Provide step-by-step instructions for reviewers to test -->+1. Step 1+2. Step 2+3. Expected result:----## 📋 Related Issues-Link any related GitHub issues (use keywords like `Fixes #issue_number` to automatically close them when the PR is merged):-- Fixes #-- Closes #+## 📊 Performance Impact++### Performance Considerations+<!-- Check all that apply -->+- [ ] No performance impact expected+- [ ] Performance improvement expected+- [ ] Performance regression possible (explained below)+- [ ] Performance testing required++### Benchmarks+<!-- If applicable, provide before/after performance metrics -->+| Metric | Before | After | Change |+|--------|--------|-------|--------|+| Load time | - | - | - |+| Memory usage | - | - | - |+| CPU usage | - | - | - |----## ✅ Checklist-Before submitting your PR, ensure the following:-- [ ] Code conforms to the project's style and guidelines.-- [ ] Changes have been tested locally.-- [ ] Relevant documentation has been updated.-- [ ] All tests pass successfully.+## 🔄 Breaking Changes++### Breaking Changes+<!-- List any breaking changes and migration instructions -->+- [ ] No breaking changes+- [ ] Breaking changes present (detailed below)++<!-- If breaking changes exist, provide details: -->+**Migration Guide:**+1. Step 1+2. Step 2++**Affected APIs/Features:**+- API endpoint X changed from Y to Z+- Configuration option A renamed to B----## 📷 Screenshots or Demos (Optional)-Attach any screenshots or screen recordings that demonstrate the changes, if applicable.+## ✅ Pre-Submission Checklist++### Code Quality+- [ ] Code follows the project's style guidelines+- [ ] Self-review of code completed+- [ ] Code is well-commented, particularly in hard-to-understand areas+- [ ] No debug statements or commented-out code left behind+- [ ] Error handling is appropriate and consistent++### Documentation+- [ ] README updated (if needed)+- [ ] API documentation updated (if needed)+- [ ] Inline code documentation added/updated+- [ ] CHANGELOG.md updated (if applicable)+- [ ] Migration guide provided (for breaking changes)++### Testing+- [ ] All existing tests pass+- [ ] New tests added for new functionality+- [ ] Edge cases covered in tests+- [ ] Manual testing completed+- [ ] Cross-browser testing done (if frontend changes)++### Dependencies & Security+- [ ] No new security vulnerabilities introduced+- [ ] Dependencies are up-to-date and necessary+- [ ] No sensitive information exposed in code+- [ ] License compatibility checked for new dependencies++### Deployment & CI+- [ ] CI/CD pipeline passes+- [ ] Docker build succeeds (if applicable)+- [ ] Database migrations work correctly (if applicable)+- [ ] Environment variables documented (if new ones added)++---++## 📷 Visual Changes+<!-- Include screenshots/videos for UI changes -->++### Before+<!-- Screenshot/description of current state -->++### After+<!-- Screenshot/description of new state -->++---++## 🤔 Review Focus Areas+<!-- Guide reviewers on what to focus on -->+Please pay special attention to:+- [ ] Algorithm correctness in `function_name()`+- [ ] Error handling in edge cases+- [ ] Performance implications of the new feature+- [ ] Security considerations for user input validation+- [ ] Backward compatibility++---++## 📚 Additional Context++### Design Decisions+<!-- Explain any significant design decisions made -->+++### Alternative Approaches+<!-- Mention alternative approaches considered and why they were not chosen -->+++### Future Considerations+<!-- Any follow-up work or future improvements planned -->+++### Dependencies+<!-- List any dependencies this PR has on other PRs or external factors -->+- Depends on PR #XXX+- Requires deployment of service Y+- Needs configuration update in environment Z++---++## 🚀 Deployment Notes+<!-- Any special instructions for deployment -->+- [ ] No special deployment steps required+- [ ] Database migration required+- [ ] Configuration changes required+- [ ] Service restart required+- [ ] Cache clearing required++**Deployment Instructions:**+1. Step 1+2. Step 2----## 📚 Additional Information-Include any additional details about the changes, potential challenges, or areas needing further review.+## 🔍 Post-Merge Checklist+<!-- Items to check after merging -->+- [ ] Monitor application performance+- [ ] Check error logs for new issues+- [ ] Verify feature works in production+- [ ] Update project board/roadmap+- [ ] Notify stakeholders of changes----**Thank you for your contribution to Fincept Terminal! 🙌**+**Thanks for contributing to Fincept Terminal! 🚀**++<!--+Reviewer Guidelines:+- Review code for logic, style, and best practices+- Test the changes locally if possible+- Check that all checklist items are completed+- Provide constructive feedback+- Approve when satisfied with the quality+-->\ No newline at end of filediff --git a/.github/workflows/docker-image.yml b/.github/workflows/docker-image.ymlindex 3f53646d1..78240f9dd 100644--- a/.github/workflows/docker-image.yml+++ b/.github/workflows/docker-image.yml@@ -5,14 +5,98 @@ on:branches: [ "main" ]pull_request:branches: [ "main" ]+ workflow_dispatch: # Allow manual triggering-jobs:+env:+ REGISTRY: ghcr.io+ IMAGE_NAME: ${{ github.repository }}+jobs:build:+ runs-on: ubuntu-latest+ permissions:+ contents: read+ packages: write++ steps:+ - name: Checkout repository+ uses: actions/checkout@v4++ - name: Set up Docker Buildx+ uses: docker/setup-buildx-action@v3++ - name: Log in to Container Registry+ if: github.event_name != 'pull_request'+ uses: docker/login-action@v3+ with:+ registry: ${{ env.REGISTRY }}+ username: ${{ github.actor }}+ password: ${{ secrets.GITHUB_TOKEN }}++ - name: Extract metadata+ id: meta+ uses: docker/metadata-action@v5+ with:+ images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}+ tags: |+ type=ref,event=branch+ type=ref,event=pr+ type=sha,prefix={{branch}}-+ type=raw,value=latest,enable={{is_default_branch}}++ - name: Build and push Docker image+ uses: docker/build-push-action@v5+ with:+ context: .+ file: ./Dockerfile+ push: ${{ github.event_name != 'pull_request' }}+ tags: ${{ steps.meta.outputs.tags }}+ labels: ${{ steps.meta.outputs.labels }}+ cache-from: type=gha+ cache-to: type=gha,mode=max+ platforms: linux/amd64,linux/arm64+ test:runs-on: ubuntu-latest+ needs: build+ if: github.event_name == 'pull_request'steps:- - uses: actions/checkout@v4- - name: Build the Docker image- run: docker build . --file Dockerfile --tag my-image-name:$(date +%s)+ - name: Checkout repository+ uses: actions/checkout@v4++ - name: Set up Docker Buildx+ uses: docker/setup-buildx-action@v3++ - name: Build test image+ uses: docker/build-push-action@v5+ with:+ context: .+ file: ./Dockerfile+ load: true+ tags: test-image:latest+ cache-from: type=gha++ - name: Test Docker image+ run: |+ echo "Testing if container starts successfully..."+ docker run --rm test-image:latest python -c "print('Container test passed!')"++ security-scan:+ runs-on: ubuntu-latest+ needs: build+ if: github.event_name != 'pull_request'++ steps:+ - name: Run Trivy vulnerability scanner+ uses: aquasecurity/trivy-action@master+ with:+ image-ref: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }}+ format: 'sarif'+ output: 'trivy-results.sarif'++ - name: Upload Trivy scan results to GitHub Security tab+ uses: github/codeql-action/upload-sarif@v3+ if: always()+ with:+ sarif_file: 'trivy-results.sarif'\ No newline at end of filediff --git a/.github/workflows/metrics.yml b/.github/workflows/metrics.ymldeleted file mode 100644index e69de29bb..000000000diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.ymldeleted file mode 100644index 929c97477..000000000--- a/.github/workflows/publish.yml+++ /dev/null@@ -1,32 +0,0 @@-name: Publish Python Package--on:- push:- tags:- - 'v*' # Triggers the workflow on version tags like v1.0.0--jobs:- build:- runs-on: ubuntu-latest-- steps:- - name: Check out the code- uses: actions/checkout@v4-- - name: Set up Python- uses: actions/setup-python@v5- with:- python-version: '3.11' # Specify the Python version you are using-- - name: Install dependencies- run: |- python -m pip install --upgrade pip- pip install build-- - name: Build the package- run: python -m build-- - name: Publish to PyPI- uses: pypa/gh-action-pypi-publish@release/v1- with:- password: ${{ secrets.PYPI_API_TOKEN }}diff --git a/.gitignore b/.gitignoreindex df60d217a..062fa215c 100644--- a/.gitignore+++ b/.gitignore@@ -11,7 +11,8 @@ build.txtcmderreqgen.pyfincept_env-fincept_terminal/testing+python+testingfincept_terminal/fyers_session_config.jsonfincept_terminal/backup_20250730_072611.pdm-build@@ -19,10 +20,12 @@ fincept_terminal.egg-infoFinceptTerminal.specfincept_terminal_structure.txtOutput+launcher.cppte+.venvfincept.batpdm.lock-vin+FinceptTerminal.exefincept_terminal/settings.jsonfincept_terminal/watchlist_settings.jsonupx.exediff --git a/pyproject.toml b/pyproject.tomlindex baf15755d..c22a2ea28 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -1,6 +1,6 @@[project]name = "fincept-terminal"-version = "1.0.10"+version = "2.0.4"description = "A Terminal for Financial Market Analysis and Fetching all kinds of Data."readme = "README.md"authors = [