A sophisticated, semi-automated chatbot for smarter TWSE 臺灣證券交易所 investing. Designed for busy investors, it offers customizable analysis and open-source collaboration, ideal for those with development skills
#3#6
Create a crawler to automate the retrieval of the company list, replacing the current manual process. The crawler will extract company data from online sources and store it in our database through the database API.
The goal of this issue is to develop detailed documentation to assist new developers in joining and contributing to our project. The documentation should cover all aspects necessary for a new contributor to get up to speed, including setup instructions, project architecture, coding standards, key functionalities, and a guide to making contributions. This document will serve as a valuable resource for onboarding new team members and ensuring consistent understanding and approach across the development team.
#3
The enhancement involves updating the mops-crawler's logic to extract, and process cash flow / income statements. And also database-api's logic to store the data.
The current /stock commands is limited to ticker symbols, hindering user experience. It needs an update to allow input of stock names in addition to ticker symbols for more intuitive and flexible use.
Command Syntax: /stockinfo [ticker_symbol or stock_name] Example: /stockinfo 2330 or /stockinfo 台積電.
Expected Output:
Stock Name and Ticker Symbol: To confirm to the user which stock they are viewing.
Current Price/Close Price: If the market is open, show the current trading price. If the market is closed, show the last closing price.
52-Week High: The highest price at which the stock has traded during the last 52 weeks.
52-Week Low: The lowest price at which the stock has traded during the last 52 weeks.
#3
When mops-crawler exceeds the rate limit of MOPS, it encounters a 429 error, leading to service disruption. The task involves implements a retry logic (maybe with exponential backoff?)
GitHub does not count contributions on a fork repo. The upstream repo https://github.com/WildfootW/TradeWiSE is the old repo where we migrated from, and all new updates are on this one. And since we do not plan to merge into the upstream, maybe we should detach and convert this repo to a normal repo.
Possible impacts:
PR & issue references to the old repo become dangling
The objective of this issue is to evaluate and potentially transition our project's dependency management from Pip to Poetry. This change aims to leverage Poetry's advanced features such as better dependency resolution, easier publishing of packages, and its ability to handle both dependencies and packaging. A comparative analysis of Pip and Poetry will be conducted, focusing on key aspects like ease of use, performance, compatibility, and community support. The outcome of this analysis will guide the decision on whether to proceed with the transition.