🔧 enable ajv strict mode and fix view schema type declaration

- Add `strict: true` to Ajv options to surface schema issues earlier
- Add `allowUnionTypes: true` to relax the strict mode rule disallowing union
  types, since the schemas use them intentionally
- Wrap `ajv.validate()` in a try/catch to report schema-level errors (e.g.
  unknown keywords) without crashing, since strict mode can throw instead of
  returning false
- Add `"type": "object"` to the `view` property in view-schema.json, which
  strict mode now requires

Author: BenoitZugmeyer

schemas/rum/view-schema.json

@@ -27,6 +27,7 @@
           "readOnly": true
         },
         "view": {
+          "type": "object",
           "required": ["time_spent", "action", "error", "resource"],
           "properties": {
             "time_spent": { "type": "integer" },

scripts/validate.mjs

@@ -90,15 +90,26 @@ function validateSchemasIds() {
 
 function validateSamples() {
   const ajv = new Ajv({
+    strict: true,
     // By default, ajv objects to heterogeneous tuples; the reasoning is that
     // they are awkward to work with in some languages. Disable this warning
     // since we're using this feature extensively and are aware of the tradeoffs.
     strictTuples: false,
+    allowUnionTypes: true,
   })
   forEachFile(SCHEMAS_DIRECTORY, (schemaPath) => ajv.addSchema(readJson(schemaPath)))
   forEachFile(SAMPLES_DIRECTORY, (samplePath) => {
     const schemaId = computeSchemaIdFromSamplePath(samplePath)
-    const valid = ajv.validate(schemaId, readJson(samplePath))
+    let valid
+    try {
+      valid = ajv.validate(schemaId, readJson(samplePath))
+    } catch (error) {
+      console.log(`❌ ${samplePath} had a validation error against ${schemaId}:`)
+      console.log(`   - ${error.message}`)
+      process.exitCode = 1
+      return
+    }
+
     if (valid) {
       console.log(`✅ ${samplePath}`)
     } else {