fix emojies

This commit is contained in:
Dobromir Popov
2025-11-22 21:46:35 +02:00
parent e541e16e7e
commit 9a06288911
37 changed files with 528 additions and 181 deletions

View File

@@ -5,6 +5,9 @@
## Unicode and Encoding Rules
- **NEVER use Unicode characters that may not be supported by Windows console (cp1252)**
- **ABSOLUTELY NO EMOJIS** in any code, logs, or console output (e.g., ✅, ✓, ❌, ⚠️, 🚀, 📊, 💾, 🔄, ⏳, 🎯, 📈, 📉, 🔍, ⚡, 💡, 🛠️, 🔧, 🎉, ⭐, 📁, 📋)
- Use plain ASCII text for all log messages, print statements, and console output
- Replace emojis with descriptive text (e.g., "OK", "ERROR", "WARNING", "SUCCESS")
## Code Structure and Versioning Rules
@@ -24,14 +27,18 @@
## Logging Best Practices
- Use structured logging with clear, ASCII-only messages
- **NEVER use emojis or Unicode symbols in log messages**
- Include relevant context in log messages without Unicode characters
- Use logger.info(), logger.error(), etc. with plain text
- Use logger.info(), logger.error(), etc. with plain text only
- Use descriptive prefixes instead of emojis (e.g., "SUCCESS:", "ERROR:", "WARNING:")
- Example: `logger.info("TRADING: Starting Live Scalping Dashboard at http://127.0.0.1:8051")`
- Example: `logger.info("SUCCESS: Model checkpoint loaded successfully")`
## Error Handling
- Always include proper exception handling
- Log errors with ASCII-only characters
- Provide meaningful error messages without emojis
- Log errors with ASCII-only characters - **NO EMOJIS**
- Provide meaningful error messages using plain text descriptors
- Use text prefixes like "ERROR:", "FAILED:", "WARNING:" instead of emoji symbols
- Include stack traces for debugging when appropriate
## File Naming Conventions
@@ -59,8 +66,10 @@
## Code Review Checklist
Before submitting code changes, verify:
- [ ] No Unicode/emoji characters in logging or console output
- [ ] **ABSOLUTELY NO EMOJIS OR UNICODE SYMBOLS** in any code, logs, or output
- [ ] All log messages use plain ASCII text only (logger.info, logger.error, print, etc.)
- [ ] No duplicate implementations of existing functionality
- [ ] Proper error handling with ASCII-only messages
- [ ] Windows compatibility maintained
- [ ] Existing code structure preserved and enhanced rather than replaced
- [ ] Windows compatibility maintained (PowerShell console safe)
- [ ] Existing code structure preserved and enhanced rather than replaced
- [ ] Use descriptive text instead of symbols: "OK" not "✓", "ERROR" not "❌", "SUCCESS" not "✅"