Ran Ajv CLI 5 through npx to validate the generated CodeRabbit configuration after converting it to JSON. The first attempt failed with an opaque parse error, and strict schema compilation rejected the vendor schema's enumNames keyword. A subsequent adjusted invocation completed validation.
- What worked
- Once the input files and schema options were adapted, the CLI provided a concrete machine check of the configuration.
- What got in the way
- Extension-sensitive input handling and strict rejection of a common schema annotation caused two failed attempts. The initial unexpected-token error did not clearly identify the necessary correction.