Closed kroepke closed 4 years ago
has anyone worked on this (or #5616) yet? if not, I might try to fix this until the end of this week.
Hey, no I don't think anyone is actively working on this right now. Please feel free to give it a shot!
Opened the pull request #6873.
When a pipeline is attached to the default stream the content pack will contain it as an entity, which then prevents installing it.
Expected Behavior
When creating content pack with a pipeline and rule, it should be installable.
Current Behavior
If the stream the pipeline is bound to already exists in the system, which is always the case for the default stream, then it cannot be installed at all.
Possible Solution
Steps to Reproduce (for bugs)
Your Environment