DEV-15014: Update field blueprint prompt_config to use description#448
Merged
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Sung96kim
previously approved these changes
Mar 13, 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.

Changelog
promptConfig.descriptioninstead ofprompt.fieldConfig.validationConfigas a scalar (no subfield selection), matching current schema.descriptionusage and scalarvalidationConfigquery shape.Confluence Changelog
Changelog Summary
prompttodescription.validationConfigin field blueprint queries to matchGenericScalarschema.Contract Changes
ExtractionPromptConfigselection usesdescription.ExtractionFieldConfig.validationConfigis queried asvalidationConfig(scalar), notvalidationConfig { ... }.promptConfig.description.Backward Compatibility / Breaking Changes
promptunder prompt config.Tests and Verification Added
pytest -q tests/test_field_blueprints.pyNet New Behaviors Requiring Integration Tests
promptConfig.descriptionand scalarvalidationConfig.Note
Medium Risk
Medium risk because it changes the GraphQL contract for
promptConfig(fromprompttodescription) and altersvalidationConfigselection shape, which can break compatibility against older schemas or callers relying on the previous fields.Overview
Updates field blueprint GraphQL queries (
CreateFieldBlueprint,GetFieldBlueprints,ListFieldBlueprints) to requestpromptConfig.descriptioninstead ofprompt.Adjusts
fieldConfig.validationConfig(and relatedformatConfig/inputConfig) to be queried as scalar fields rather than selecting subfields, and expands tests to assert the new query shapes and response parsing fordescription.Written by Cursor Bugbot for commit 6199319. This will update automatically on new commits. Configure here.