feat: allow blueprints to specify preview and thumbnail containter ids in applyConfig

[ianshade]

About the Contributor

This pull request is posted on behalf of TV 2 Norge.

Type of Contribution

This is a: Feature

Current Behavior

Previously, blueprints did not have the ability to specify custom preview and thumbnail container IDs in the applyConfig method. Container IDs had to be configured manually by the user.

New Behavior

Blueprints can now specify custom preview and thumbnail container IDs directly in the applyConfig method.
Additionally a new, cleaner way of defining migrations as classes is introduced.

Testing

• I have added one or more unit tests for this PR
• I have updated the relevant unit tests
• No unit test changes are needed for this PR

Affected areas

• This PR affects blueprint configuration and preview/thumbnail container handling
• Changes apply to the applyConfig method in blueprint integration
• Migrations

Time Frame

Other Information

Status

• PR is ready to be reviewed.
• The functionality has been tested by the author. (before porting to release53)
• Relevant unit tests has been added / updated.
• Relevant documentation (code comments, system documentation) has been added / updated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

❌ Patch coverage is 71.02804% with 31 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...ations/packageManager/expectedPackages/generate.ts	0.00%	11 Missing ⚠️
...ons/packageManager/expectedPackages/publication.ts	0.00%	8 Missing ⚠️
meteor/server/api/studio/api.ts	0.00%	4 Missing ⚠️
meteor/server/migration/X_X_X.ts	57.14%	3 Missing ⚠️
meteor/server/migration/databaseMigration.ts	66.66%	2 Missing ⚠️
...ns/pieceContentStatusUI/checkPieceContentStatus.ts	66.66%	2 Missing ⚠️
...server/publications/pieceContentStatusUI/common.ts	66.66%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[Julusian]

perhaps this should be called packageContainerSettings?

Expands the scope to allow more package container related things to be put in here too if they are needed in the future.

I dont mind though

[Julusian]

At this point, the Pick<DBStudio feels rather silly. Perhaps time to drop that and define _id explicitly

[Julusian]

I think it would be good to have this in a folder matching the X_X_X naming scheme, so that we can more easily keep track of which steps are being for each version. (Which will help us when we want to clean migrations from some really old versions again)

I like the class approach though, seems like it will help with some of the duplication 'problem' that bugs me with the other approach (not enough to consider changing it though)