Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
backbone-message-format backbone-message-format
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • backbone-message-formatbackbone-message-format
  • Issues
  • #54

Closed
Open
Created Aug 20, 2024 by Dan Jones@danjonOwner

Compiled schema fails JS validation

The compiled schema no longer passes JS validation although I can't see that it's changed.

  "swagger_ui": true,
  "specs_route": "/",

are unexpected additional properties. Unlike the message validator there doesn't appear to be an option in the schema validator to accept additional properties.

The versions are all pinned so it doesn't look like it's a code change. Am pretty sure these tests all used to pass during SoAR.

I guess we have to work through the validation failures and accept some of the expected validation errors so it only fails on unexpected errors.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking