Skip to content

Conversation

@ianshade
Copy link
Collaborator

No description provided.

@chandrashekar-nallamilli
Copy link
Collaborator

Can you explain why we need to do it this way. Is it core change . any documentation that corresponds to this . The reason being , i can see existing variable now move as subvars to another variable. So basically a schema change

@ianshade
Copy link
Collaborator Author

Sofie-Automation#1263 will give you more context. Config defined by blueprints utilizes the overrides mechanism - blueprints provide the defaults, the user might override them. Overrides work on objects, hence the omnipresent ObjectWithOverrides. Since those two properties affected by this PR are very closely related, I placed them in the same object, which made it relatively simple.

Copy link
Collaborator

@chandrashekar-nallamilli chandrashekar-nallamilli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM COde wise. But not completely sure of the functionality

@ianshade ianshade merged commit ee58c34 into release52 Jul 23, 2025
31 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.

3 participants