gavindiaz/vibe-coding-cn
1
0
Fork 0
mirror of https://github.com/tradecatlabs/vibe-coding-cn.git synced 2026-08-18 05:18:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(en): remove extra files to align with zh structure

Browse Source 
- Remove Learning Experience.md from 02-methodology
- Remove telegram-dev/ from 02-methodology
- Remove fate-engine-dev/ from 03-practice
- Update 02-methodology README
This commit is contained in:
tukuaiai
2025-12-19 03:24:56 +08:00
parent fbef741768
commit d178f4f8b6
7 changed files with 0 additions and 119 deletions
Download Patch File Download Diff File Expand all files Collapse all files
i18n/en/documents/02-methodology/Learning Experience.md
-5
View File
@@ -1,5 +0,0 @@
The texts that impressed me the most
Huangdi Yinfu Jing: Sever the benefit from one source, and use the master ten times. Three repetitions day and night, and use the master ten thousand times.
Douyin says: People are driven by profit; great profit leads to great deeds, small profit to small deeds, and no profit to no deeds.
i18n/en/documents/02-methodology/README.md
-2
View File
@@ -9,6 +9,4 @@ Tools, tutorials, and development guides.
- [auggie-mcp Configuration Document](./auggie-mcp%20Configuration%20Document.md)
- [SSH via Mobile with FRP](./How%20to%20SSH%20to%20Local%20Computer%20from%20Any%20Location%20via%20Mobile%2C%20Based%20on%20FRP%20Implementation.md)
- [Gemini Headless Mode Translation Guide](./Gemini%20Headless%20Mode%20Translation%20Guide.md)
- [Learning Experience](./Learning%20Experience.md)
- [Vibe Coding Experience Collection](./vibe-coding-experience-collection.md)
- [telegram-dev/](./telegram-dev/) - Telegram development resources
i18n/en/documents/02-methodology/telegram-dev/telegram_Markdown_Code_Block_Format_Fix_Log_2025_12_15.md
-43
View File
@@ -1,43 +0,0 @@
# Telegram Markdown Code Block Format Fix Log 2025-12-15
## Problem
After completing the astrological chart generation, sending a message reports an error:
```
❌ Chart generation failed: Can't parse entities: can't find end of the entity starting at byte offset 168
```
## Cause
The Markdown code block format for the `header` message in `bot.py` is incorrect.
The original code used string concatenation, adding `\n` after ```, which caused the Telegram Markdown parser to incorrectly identify the code block boundary:
```python
# Incorrect way
header = (
"```\n"
f"{filename}\n"
"```\n"
)
```
## Fix
Changed to a triple-quoted string to ensure ``` is on a separate line:
```python
# Correct way
header = f"""Report attached
```
{filename}
{ai_filename}
```
"""
```
## Modified File
- `services/telegram-service/src/bot.py` lines 293-308
```