github-actions[bot] commented on code in PR #3503:
URL: https://github.com/apache/doris-website/pull/3503#discussion_r3008978036


##########
sidebars.ts:
##########
@@ -1161,7 +1161,18 @@ const sidebars: SidebarsConfig = {
                                         
'sql-manual/basic-element/sql-data-types/semi-structured/MAP',
                                         
'sql-manual/basic-element/sql-data-types/semi-structured/STRUCT',
                                         
'sql-manual/basic-element/sql-data-types/semi-structured/JSON',
-                                        
'sql-manual/basic-element/sql-data-types/semi-structured/VARIANT',
+                                        {
+                                            type: 'category',
+                                            label: 'VARIANT',
+                                            link: {

Review Comment:
   **Sidebar label collision:** The category `label` is `'VARIANT'` and the 
only child item is also `'VARIANT'` (the reference page). In the rendered 
sidebar, users will see `VARIANT` (opens workload guide) with a single child 
also called `VARIANT` (opens the reference). This creates a confusing "VARIANT 
→ VARIANT" hierarchy.
   
   Consider renaming the child item label to something like `'VARIANT 
Reference'` or `'VARIANT Type Reference'`. In Docusaurus, a simple string entry 
inherits the doc's sidebar_label or title, but you can override it with an 
object:
   
   ```ts
   items: [
       {
           type: 'doc',
           id: 
'sql-manual/basic-element/sql-data-types/semi-structured/VARIANT',
           label: 'VARIANT Reference',
       },
   ],
   ```
   
   The same change should be applied to 
`versioned_sidebars/version-4.x-sidebars.json` and 
`versioned_sidebars/version-3.x-sidebars.json`.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to