Update azure_ai.py
Browse files- azure_ai.py +3 -3
azure_ai.py
CHANGED
|
@@ -22,7 +22,7 @@ documentation for projects with 50,000+ GitHub stars (e.g., FastAPI, LangChain,
|
|
| 22 |
|
| 23 |
Your README output must:
|
| 24 |
- Feel like a polished, production-grade open-source project
|
| 25 |
-
- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture
|
| 26 |
- Include shields.io badges, tables, and collapsible sections where appropriate
|
| 27 |
- Be scannable: a developer should understand the project in under 60 seconds
|
| 28 |
- Never truncate — every section must be fully written
|
|
@@ -64,8 +64,8 @@ Follow this EXACT structure and do not skip any section:
|
|
| 64 |
- A Mermaid flowchart LR showing system components:
|
| 65 |
```mermaid
|
| 66 |
flowchart LR
|
| 67 |
-
A[Input Layer] --> B[Processing Layer]
|
| 68 |
-
B --> C[Output Layer]
|
| 69 |
```
|
| 70 |
- A component breakdown table after the diagram:
|
| 71 |
| Component | Role | Technology |
|
|
|
|
| 22 |
|
| 23 |
Your README output must:
|
| 24 |
- Feel like a polished, production-grade open-source project
|
| 25 |
+
- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture. Dont use any HTML tags in Mermaid also Wrap the label in double quotes
|
| 26 |
- Include shields.io badges, tables, and collapsible sections where appropriate
|
| 27 |
- Be scannable: a developer should understand the project in under 60 seconds
|
| 28 |
- Never truncate — every section must be fully written
|
|
|
|
| 64 |
- A Mermaid flowchart LR showing system components:
|
| 65 |
```mermaid
|
| 66 |
flowchart LR
|
| 67 |
+
A["Input Layer]" --> B["Processing Layer"]
|
| 68 |
+
B --> C["Output Layer"]
|
| 69 |
```
|
| 70 |
- A component breakdown table after the diagram:
|
| 71 |
| Component | Role | Technology |
|