Use callouts to highlight user action post-TF-generation #94
Conversation
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
|
🔗 Preview your changes |
bflad
previously approved these changes
Jan 9, 2026
Removed duplicate heading for implementation notes.
bflad
approved these changes
Jan 9, 2026
bradcypert
deleted the
bradcypert/callouts-for-post-generation-instructions-in-tf
branch
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.
With Validators and PlanModifiers, the user is adding the extensions to their openapi spec and are expected to re-run generation after doing so, however, that step isn't very clear. I've added the Callout component to hopefully make that more apparent and changed the wording a bit to be easier to follow.