Feature/cmcdv2 update

[littlespex]

No description provided.

[gemini-code-assist]

Warning

Gemini encountered an error creating the summary. You can try again by commenting /gemini summary.

[littlespex]

@nicolaslevy @cotid-qualabs These changes are ready to merge, but I noticed something when reviewing the CMCD event reports: When no events or keys are provided, the current code treats that as "All keys/events enabled". We moved away from this approach in CML for 2 reasons:

1. There are so many new keys and events in v2, so defaulting to everything seems like too much.
2. It is easier to reason about the code base when an empty array simply means "nothing", instead of it being a special case that actually means "everything".

Was this functionality added in the initial v2 changes, or was this how it worked in previous versions of dash.js with CMCD v1 support?

[cotid-qualabs]

@littlespex We implemented that behavior in the first approach we took for CMCDv2, but it seems we missed updating it after it became deprecated. We will update the behavior on this branch if that’s okay

[cotid-qualabs]

Just to be aligned, the updated behavior is:

• If no events are defined (or the array is empty), no reports are sent.
• If no keys are defined (or the array is empty), only mandatory keys are sent.

Combinations:

• No events + defined keys → no report is sent.
• Events + undefined keys → only mandatory keys are sent.
• No events + no keys → no report is sent.
• Events + keys → a report is sent.

Is this correct?

[littlespex]

That is the correct behavior.