Project packaging

Ignition
1

Hi all,

Our Ignition projects are organized like this:
We have 1 parent 'lib' project, and then a few children projects underneath, often different teams managing other children-projects.

However, lately, we get this question more often: Can we make it so our 'lib' project get's updated for one child project and not for another, so we can really use our lib-project as a code-package?
So for example 1 department would still run lib-project V2, while another department would run lib-project V3, so the first department can take their time to test the newer version before it is auto-pushed.

One idea we have is to have 1 dev-lib project, but deploy it to project1-lib and project2-lib project on our production env.

I wonder if anyone has a solid way of tackling this.
Thanks!

2

No. (You are basically asking for multiple inheritance, which isn't happening anytime soon, if ever.)

The approach I recommend is to override that resource in a dev project, make and thoroughly test the changes, then send it back to the parent project.

1 Like