Copilot commented on code in PR #12869:
URL: https://github.com/apache/trafficserver/pull/12869#discussion_r2819087634


##########
doc/admin-guide/configuration/hrw4u.en.rst:
##########
@@ -158,7 +176,7 @@ Syntax               Free-form                     
Structured `if (...) { ... }`
 Conditions           `cond %{...}`                 Implicit in `if (...)`
 Operators            Raw text (`set-header`)       Structured assignments or 
statements
 Grouping             `GROUP` / `GROUP:END`         Use `()` inside `if` 
expressions
-Else branches        `else` with indented ops      `else { ... }` with full 
block
+Else branches        `else` with indented ops      `elif ... { ... }` and 
`else { ... }` with full blocks
 Debugging            Manual with logs              Built-in debug tracing 
(`--debug`)

Review Comment:
   This simple-table row likely exceeds the column width for the HRW4U column, 
which can break reStructuredText table parsing/rendering. Please wrap the HRW4U 
cell onto an indented continuation line (aligned with the start of the HRW4U 
column) or widen the table separator line so the column is wide enough.



##########
doc/admin-guide/configuration/hrw4u.en.rst:
##########
@@ -94,10 +94,10 @@ Syntax Differences
 ==================
 
 The basic structure is a `section` name defining the part of the transaction 
to run in
-followed by conditionals and operators. It uses `if () {} else {}` conditional 
syntax
+followed by conditionals and operators. It uses `if () {} elif () {} else {}` 
conditional syntax
 with `&& , || and ==`, with conditions and operators generally following 
function() or

Review Comment:
   The inline syntax example uses `if () {}` / `elif () {}` with empty 
conditions, which reads like valid code but isn’t valid HRW4U syntax. Consider 
using an ellipsis placeholder (e.g., `if (...) { ... } elif (...) { ... } else 
{ ... }`) to avoid implying empty conditions are allowed.



-- 
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]

Reply via email to