fix(preflight): preserve one-page FIELD values#1186
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying quickadd with
|
| Latest commit: |
94825ef
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://402ec749.quickadd.pages.dev |
| Branch Preview URL: | https://1184-bug-one-page-input-doub.quickadd.pages.dev |
Preserve one-page input values for
{{FIELD:...}}tokens by using the runtime-compatibleFIELD:key during preflight collection. This prevents Template choices from prompting a second time after the one-page modal has already collected the FIELD value.The field suggestion UI still displays raw labels and strips the internal prefix before parsing, so vault suggestions continue to work for both plain and filtered FIELD syntax.
Validation performed:
bun run testbun run lintbun run build{{FIELD:People}}and{{FIELD:People|folder:Contacts}}, confirming prefixed variables resolve and generated output contains the provided values with no dev errors.Fixes #1184