fix: omit privateData in bucket adlib pieces and actions publications #1389
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the Contributor
This pull request is posted on behalf of TV 2 Norge
Type of Contribution
This is a:
Bug fix
Current Behavior
Bucket AdLib Pieces' and Bucket AdLib Actions'

privateData
is exposed to the frontend via publications.There are no defined constraints regarding what can be placed in
privateData
of Bucket AdLib Pieces and Bucket AdLib Actions, however if any (sub)property within it starts with a$
, minimongo will throw on the frontend, and some parts of the UI will refuse to render (likely just the contents of the bucket). It's a common practice [citation needed] to store entire Pieces generated ahead of time, including their timeline objects (which oftentimes contain a$references
property), inprivateData
of AdLib Actions, therefore this bug is likely to occur for anyone who does that in their blueprints. Besides that, it may also have some performance impact, depending on the size of privateData.New Behavior
Bucket AdLib Pieces' and Bucket AdLib Actions'
privateData
is not exposed to the frontend via publications.Testing
Affected areas
This PR affects the Buckets area in the UI, and potentially any other DDP clients that may use related publications.
Time Frame
We consider this to be a bug worthy of fixing in release52, before it reaches the stable phase
Other Information
Status