feat: form column scaffold applier for pp-form-column - #91
Open
zekelinAlex wants to merge 1 commit into
Open
Conversation
This was referenced Sep 11, 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
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.
Adds the FormColumn applier for pp-form-column and exposes ResolveTab on the shared placement resolver. One quirk kept on purpose: the old script resolves the tab footer document-wide (//tabfooter, with an undefined tabFooterId variable on top), so the applier does the same - the parity run confirmed identical output for the footer variant.
Stacked on #90, merge after it. Sandbox parity: byte-identical against the old scripts, the only diff is the form-id-only variant that the old locator crashed on (now works), and the dialog + footer scenario matched byte for byte.