Repository navigation
Allow all fields in the values section and make output optional - #19
Merged
Merged
Conversation
matthdsm
approved these changes
Nov 5, 2026
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
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.
This pull request introduces several improvements and changes to the worksheet handling logic, making the
outputsection optional and unifying data field references across worksheet sections. The changes increase flexibility in worksheet configuration, especially for pipelines focused on quality checking, and standardize how data fields are accessed and validated throughout the codebase.Worksheet Configuration and Data Handling:
outputsection of the worksheet optional, updating related logic and schema validation to reflect this change. This allows for worksheets that do not require an output section, which is particularly useful for quality control pipelines. [1] [2]input,output,metrics, andvaluessections by introducing adataFieldsset and changing the context object frominputtodatathroughout the codebase. [1] [2] [3] [4] [5] [6] [7] [8]User-Facing Documentation and Examples:
dataobject instead ofinput, and to demonstrate the new flexibility in field references. [1] [2]Testing and Error Messages:
datafields instead ofinputfields, ensuring consistency and clarity for users.Changelog: