feat: policy table output type - #481
Merged
Merged
Conversation
ivanmiletic
approved these changes
Jul 10, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Typed output columns for decision tables
Decision-table output columns can now declare a type:
string,number,boolean,dateor a dictionary name, optionally suffixed with[]for lists. The annotation is optional; untyped columns keep the existing inferred behavior.When a column is typed, every non-null cell is checked against the declaration, with diagnostics anchored to the offending cell. The declared type also becomes the column's output schema instead of a merge of cell types (nullable when uncovered), and unknown or malformed annotations are diagnosed on the column head. Dictionary-typed cells additionally get labeled select options in the natural-language projection, single or multi depending on
[].Business Value
Output types become stated intent rather than an accident of whatever cells currently contain. A typo in one cell is a local diagnostic instead of a silently widened column type, downstream blocks see a stable schema while rows are edited, and dictionaries now constrain table outputs the same way they constrain inputs. Purely additive.