Motivation

PR #306 introduced a change in the rum-events-schemas (making the view event property optional for the "App Launch" vital) that is causing some issues within the Browser.

Even though the view property was marked as "required" on events that requires it, this is badly supported by the json-schema-to-typescript and the view property was still optional on some events (ex: long task, resource...).

On top of this, even if the typescript generation did work correctly, the RumEvents union that is exposed to customers via beforeSend would still have an optional view property since it includes the "App Launch" vital. That would be a breaking change for customers using typescript. In the following example, TypeScript would raise a "'event.view' is possibly 'undefined'." error:

DD_RUM.init({
  beforeSend(event) {
    event.view.url = removeSensitiveData(url)
  }
})

Related Browser SDK PR based on this change: DataDog/browser-sdk#3923

Changes

To work around this issue, this PR changes how vital schema are declared. Instead of using a single schema for the vital event and a different schema for the vital property, it declares one schema for each type of vital event.

This allows to tweak each vital event independently, and make the view property optional only on the App Launch vital.

This also allows to expose a different RumEvent union to be consumed by mobile and browser. For browser, the RumEvent union does not include the App Launch vital event, so all events have a required view property.

Finally, it adds a workaround to make sure the TypeScript generation makes view properties required when needed. It adds a validation rule to make sure this workaround is always enforced.

The first two commits are just small maintenance changes related to vital events.