Skip to content

Add support for nested steps and grouping in FormFlowType#7

Merged
yceruto merged 5 commits into
mainfrom
nested_steps
May 11, 2026
Merged

Add support for nested steps and grouping in FormFlowType#7
yceruto merged 5 commits into
mainfrom
nested_steps

Conversation

@yceruto
Copy link
Copy Markdown
Owner

@yceruto yceruto commented May 11, 2026

  • Bump minimum PHP version to 8.4
  • Introduce createStepGroup method in FormFlowBuilderInterface
  • Implement setGroup, addStep, and removeStep methods in FlowStepBuilderInterface
  • Add isGroup, getSteps, hasStep, and getStep methods in FlowStepConfigInterface
  • Include with_reset option in FlowNavigatorType for conditional reset button
  • Enhance FlowCursor to handle nested step structures
  • Update FormFlowType to support new view variables for nested steps

- Bump minimum PHP version to 8.4
- Introduce createStepGroup method in FormFlowBuilderInterface
- Implement setGroup, addStep, and removeStep methods in FlowStepBuilderInterface
- Add isGroup, getSteps, hasStep, and getStep methods in FlowStepConfigInterface
- Include with_reset option in FlowNavigatorType for conditional reset button
- Enhance FlowCursor to handle nested step structures
- Update FormFlowType to support new view variables for nested steps
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented May 11, 2026

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
16496482 Triggered Generic Password aeac4a9 tests/Flow/FormFlowTest.php View secret
16496482 Triggered Generic Password aeac4a9 tests/Flow/FormFlowTest.php View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@yceruto yceruto merged commit 3c402fe into main May 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant