Skip to content

OpenAPI Diff reports Compare specs completed after parse failure #354

Description

@baixiangcpp

Summary

When one OpenAPI input is invalid, OpenAPI Diff shows the parse error and disables Copy/Download, but the action status still says Compare specs completed.. The success status is misleading after a failed comparison.

Affected route: https://byteflow.tools/en/openapi-diff

Reproduction

  1. Click Clear.

  2. Put this invalid JSON in the first spec:

    {"openapi":
    
  3. Put this valid minimal spec in the second input:

    {"openapi":"3.0.3","info":{"title":"T","version":"1"},"paths":{}}
    
  4. Click Compare specs.

Expected

  • show the parse error;
  • show a failure/error status, or clear the previous success status;
  • keep Copy and Download disabled.

Actual

  • Unexpected end of JSON input is shown;
  • Copy and Download are disabled;
  • the status still reads Compare specs completed..

The output itself was empty after the invalid comparison; this report is specifically about the contradictory success status.

Environment

  • Browser: Chrome via cloud browser
  • Tested: 2026-08-18

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions