[codex] Update emotion control page for S2 tags#82
Conversation
📝 WalkthroughWalkthroughThe PR updates the Emotion Control documentation to introduce S2 syntax, replacing S1 parenthesis-based markers with square-bracket cues. The main documentation page is rewritten across all sections—imports, usage guidance, placement rules, advanced techniques, best practices, and reference tables—while five new reference snippet files define emotion, effect, and tone mappings for the S2 system. ChangesEmotion Control S2 Syntax Migration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
🧹 Nitpick comments (5)
snippets/emotion-list-basic-s2.mdx (1)
1-27: 💤 Low valueConsider adding frontmatter to snippet files.
While this is an imported snippet rather than a standalone page, the coding guidelines state "Do not skip frontmatter on any MDX file." Consider adding minimal frontmatter with a title for consistency, even if the snippet is only used via imports.
As per coding guidelines: "Do not skip frontmatter on any MDX file".
📝 Suggested frontmatter addition
+--- +title: "Basic Emotions Reference (S2)" +--- + | Emotion | Tag | Description | Example Context |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@snippets/emotion-list-basic-s2.mdx` around lines 1 - 27, This MDX snippet file (snippets/emotion-list-basic-s2.mdx) is missing YAML frontmatter; add minimal frontmatter at the very top of the file using the triple-dash block (---) and include at least a title field (for example title: "Emotion List — Basic S2") so the file complies with the "Do not skip frontmatter on any MDX file" guideline and can be imported consistently.snippets/emotion-list-advanced-s2.mdx (1)
1-28: 💤 Low valueConsider adding frontmatter to snippet files.
Similar to the basic emotions snippet, consider adding minimal frontmatter for consistency with the guideline that applies to all MDX files.
As per coding guidelines: "Do not skip frontmatter on any MDX file".
📝 Suggested frontmatter addition
+--- +title: "Advanced Emotions Reference (S2)" +--- + | Emotion | Tag | Description | Example Context |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@snippets/emotion-list-advanced-s2.mdx` around lines 1 - 28, This MDX snippet is missing frontmatter; add minimal YAML frontmatter at the top of emotion-list-advanced-s2.mdx (above the table that starts with "| Emotion | Tag | Description | Example Context |") — include at least a title and description (for example: title: "Advanced Emotion List" and description: "Extended list of emotion tags for snippets"), and any required canonical fields your project expects (e.g., draft: false or tags: [snippets]) so the file complies with the "Do not skip frontmatter on any MDX file" guideline.snippets/emotion-list-special-s2.mdx (1)
1-8: 💤 Low valueConsider adding frontmatter to snippet files.
As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.
As per coding guidelines: "Do not skip frontmatter on any MDX file".
📝 Suggested frontmatter addition
+--- +title: "Special Effects Reference (S2)" +--- + | Effect | Tag | Description |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@snippets/emotion-list-special-s2.mdx` around lines 1 - 8, Add a minimal YAML frontmatter block to the top of this MDX snippet (emotion-list-special-s2.mdx) so it follows the MDX guidelines; include at least a title and a type/collection field (e.g., title: "Emotion List Special S2" and type: "snippet" or collection: "emotion-snippets") before the table starting with the "Effect | Tag | Description" header, ensuring the file now begins with the frontmatter block and then the existing table content.snippets/emotion-list-tones-s2.mdx (1)
1-8: 💤 Low valueConsider adding frontmatter to snippet files.
As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.
As per coding guidelines: "Do not skip frontmatter on any MDX file".
📝 Suggested frontmatter addition
+--- +title: "Tone Markers Reference (S2)" +--- + | Tone | Tag | Description | When to Use |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@snippets/emotion-list-tones-s2.mdx` around lines 1 - 8, This MDX snippet that starts with the table header "Tone" is missing the required YAML frontmatter; add a minimal frontmatter block at the top of the file (e.g., --- title: "Emotion List: Tones S2" slug: "emotion-list-tones-s2" ---) following the project's MDX frontmatter conventions so the file is consistent with other emotion snippets and the "Do not skip frontmatter on any MDX file" guideline.snippets/emotion-list-effects-s2.mdx (1)
1-13: 💤 Low valueConsider adding frontmatter to snippet files.
As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.
As per coding guidelines: "Do not skip frontmatter on any MDX file".
📝 Suggested frontmatter addition
+--- +title: "Audio Effects Reference (S2)" +--- + | Effect | Tag | Description | Suggested Text |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@snippets/emotion-list-effects-s2.mdx` around lines 1 - 13, Add a minimal YAML frontmatter block at the very top of the MDX file (above the table starting with "| Effect | Tag | Description | Suggested Text |") containing required metadata per guidelines (e.g., a title and any required fields like layout/description or snippet identifier) so the file matches other emotion snippets; ensure the frontmatter is valid YAML and sits before any Markdown/MDX content.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@snippets/emotion-list-advanced-s2.mdx`:
- Around line 1-28: This MDX snippet is missing frontmatter; add minimal YAML
frontmatter at the top of emotion-list-advanced-s2.mdx (above the table that
starts with "| Emotion | Tag | Description | Example Context |") — include at
least a title and description (for example: title: "Advanced Emotion List" and
description: "Extended list of emotion tags for snippets"), and any required
canonical fields your project expects (e.g., draft: false or tags: [snippets])
so the file complies with the "Do not skip frontmatter on any MDX file"
guideline.
In `@snippets/emotion-list-basic-s2.mdx`:
- Around line 1-27: This MDX snippet file (snippets/emotion-list-basic-s2.mdx)
is missing YAML frontmatter; add minimal frontmatter at the very top of the file
using the triple-dash block (---) and include at least a title field (for
example title: "Emotion List — Basic S2") so the file complies with the "Do not
skip frontmatter on any MDX file" guideline and can be imported consistently.
In `@snippets/emotion-list-effects-s2.mdx`:
- Around line 1-13: Add a minimal YAML frontmatter block at the very top of the
MDX file (above the table starting with "| Effect | Tag | Description |
Suggested Text |") containing required metadata per guidelines (e.g., a title
and any required fields like layout/description or snippet identifier) so the
file matches other emotion snippets; ensure the frontmatter is valid YAML and
sits before any Markdown/MDX content.
In `@snippets/emotion-list-special-s2.mdx`:
- Around line 1-8: Add a minimal YAML frontmatter block to the top of this MDX
snippet (emotion-list-special-s2.mdx) so it follows the MDX guidelines; include
at least a title and a type/collection field (e.g., title: "Emotion List Special
S2" and type: "snippet" or collection: "emotion-snippets") before the table
starting with the "Effect | Tag | Description" header, ensuring the file now
begins with the frontmatter block and then the existing table content.
In `@snippets/emotion-list-tones-s2.mdx`:
- Around line 1-8: This MDX snippet that starts with the table header "Tone" is
missing the required YAML frontmatter; add a minimal frontmatter block at the
top of the file (e.g., --- title: "Emotion List: Tones S2" slug:
"emotion-list-tones-s2" ---) following the project's MDX frontmatter conventions
so the file is consistent with other emotion snippets and the "Do not skip
frontmatter on any MDX file" guideline.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 66552ee0-4bc1-4b73-8dd8-0318425dc10c
📒 Files selected for processing (6)
developer-guide/core-features/emotions.mdxsnippets/emotion-list-advanced-s2.mdxsnippets/emotion-list-basic-s2.mdxsnippets/emotion-list-effects-s2.mdxsnippets/emotion-list-special-s2.mdxsnippets/emotion-list-tones-s2.mdx
Summary
Validation
./node_modules/.bin/prettier --check developer-guide/core-features/emotions.mdx snippets/emotion-list-basic-s2.mdx snippets/emotion-list-advanced-s2.mdx snippets/emotion-list-tones-s2.mdx snippets/emotion-list-effects-s2.mdx snippets/emotion-list-special-s2.mdxnpm run check:openapi./node_modules/.bin/mint validatecurrently fails on existing unrelated warnings for React imports insnippets/*.jsxand missing/snippets/snippet-intro.mdxfromtemp/essentials/reusable-snippets.mdx.Summary by CodeRabbit