Assigning a parameter gets stored and persisted on the next wizard step and when creating the content pack.
Current Behavior
After creating and assigning a parameter on the content pack creation wizard, going to the next step in the wizard shows the parameter as unused. Going back to the previous step shows mixed information, the parameter list shows it as used, but the entity list does not. Creating the content pack works, but the parameter is not assigned.
There are no errors in the browser console at least while running on production.
Steps to Reproduce (for bugs)
Open create content pack wizard and fill out the first screen
Create a new parameter
Assign the parameter to one of the entities
Go to the next step and see that the parameter is marked as unused
Revisiting this while installing a content pack, I can see the parameter in the installation form, so I think this is mostly a display/consistency issue.
Expected Behavior
Assigning a parameter gets stored and persisted on the next wizard step and when creating the content pack.
Current Behavior
After creating and assigning a parameter on the content pack creation wizard, going to the next step in the wizard shows the parameter as unused. Going back to the previous step shows mixed information, the parameter list shows it as used, but the entity list does not. Creating the content pack works, but the parameter is not assigned.
There are no errors in the browser console at least while running on production.
Steps to Reproduce (for bugs)
Your Environment