Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c5833f8274
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
IyeOnline
force-pushed
the
topic/neo-context-lookup
branch
from
c5833f8 to
98ebe2b
Compare
|
📦 Preview · View → · 🟢 Live Auto-updates on push |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 98ebe2b490
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
IyeOnline
force-pushed
the
topic/neo-context-lookup
branch
2 times, most recently
from
b455a7a to
271f496
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 271f49659c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
IyeOnline
force-pushed
the
topic/neo-context-lookup
branch
from
271f496 to
69255ef
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 69255ef566
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| When using the option, the context moves from `<into>.context.<field...>` to | ||
| `<into>` in the resulting event, with a new field `<output>.field` containing |
There was a problem hiding this comment.
<output> placeholder in separate docs
The separate option description says enriched data moves to <into> and adds a new field at <output>.field, but output is not documented as a parameter anywhere in this operator signature. This leaves users with an unusable field path and suggests an option that does not exist, so readers cannot reliably query the emitted metadata after enabling separate.
Useful? React with 👍 / 👎.
| context updates into historical queries. | ||
|
|
||
| ```tql | ||
| context::lookup name:string, key=field|list, [into=field, yield=field, |
There was a problem hiding this comment.
key type between synopsis and argument docs
The synopsis lists key=field|list, but the dedicated key section later documents key = field|list[field]. Because these are conflicting type shapes for multi-key lookup, users copying the top-level syntax may provide the wrong form and get invalid queries; the page should expose one canonical type in both places.
Useful? React with 👍 / 👎.
1 participant
No description provided.