Update prompt prestage recurrence options#22
Merged
Conversation
Sync feature branch with early release main updates
chastabor
pushed a commit
to chastabor/reqquest-chas
that referenced
this pull request
May 15, 2026
* Register enum types for prestage recurrence: txstate-etc/reqquest-txstate#316 * Update prompt prestage reg definition to use spec'd types, or bool for backward compat: txstate-etc/reqquest-txstate#316 * RequiresStaging smart check update to use new prestage recurrence values: txstate-etc/reqquest-txstate#316 * Update UI schema to include prestage enum, modify demo data for test: txstate-etc/reqquest-txstate#316 * Update demo default to support INVALID prestage test operation
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
1 participant
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.
Previously prestage could be configured for recurrence of false; only stage data on first prompt use, or true; where data was always restaged when prompt was loaded.
To accommodate prompts which invalidate other prompts new recurrence options of NEVER, ALWAYS, INVALID have been added, and true/false options are maintained for backward compat.
In the instance of prestage recur being set INVALID the prompt will only prestage data if that prompt is currentl flagged as invalidate. This will allow a dev to update certain data elements (maybe uncheck the 'confirmed' checkbox on a page asking for confirmation) when a previous prompt has designated a need to review a trailing prompts information by way of invalidUponChange.