There are two reasons for the abstraction:

- In this case, the child should not know anything about its parent except how to access the form group.

- This creates a reusable pattern.

This shouldn't happen since there should be only one FormProvider.

Using an input doesn't make sense here- we're using the router.

Once you run the commands I mentioned, you should have two routes:

`onboarding/payment` and `onboarding/account`