Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9f03b872fd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| </Tab> | ||
| <Tab title="Limit"> | ||
|
|
||
| Set **OrdType (`40`)** to `2` (Limit). See [Tick Size Requirements](#tick-size-requirements), [Maximum Notional Order Size By Type](#maximum-notional-order-size-by-type), and [Limit Orders](#limit-orders). |
There was a problem hiding this comment.
Point limit-order reference to an existing section
This link targets #limit-orders, but there is no heading in this page that produces that anchor, so readers cannot jump to the intended limit-order guidance from this section. Because this page is the primary reference for required tags, a dead in-page link makes the workflow harder to follow and should be corrected to an existing anchor (or a matching section should be added).
Useful? React with 👍 / 👎.
|
|
||
| <Note> | ||
|
|
||
| **OrderID (`37`)** is set to all zeros (`00000000-0000-0000-0000-000000000000`) for Pending New. The actual OrderID is assigned in the [New](#new) report. |
There was a problem hiding this comment.
Link New-report note to a resolvable anchor
The note links to #new, but this document does not define a heading with that anchor; New appears only as a tab title. As a result, the in-page navigation from this explanatory note is broken, so readers cannot jump directly to the New response details from here.
Useful? React with 👍 / 👎.
No description provided.