Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6540

x-data-threescale-name is broken

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Minor Minor
    • None
    • 2.9.1 GA
    • System
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Undefined
    • Hide

      Currently working on swagger 2.0 and here is a sample gist https://gist.github.com/VinayBhalerao/e7ccf98c0d30d310bcfe0826b02575f9

       

      Even after adding the extension "x-data-threescale-name": "user_keys" the auto-fill for user_key doesn't work from both admin portal and developer portal active docs

       

      Expected result:

      The auto-fill should work for 2.0. 

       

      Documentation:

      https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.6/html/using_the_developer_portal/create-activedocs-spec

       

      I think the migration from swagger > open API broke the extension.

      Show
      Currently working on swagger 2.0 and here is a sample gist https://gist.github.com/VinayBhalerao/e7ccf98c0d30d310bcfe0826b02575f9   Even after adding the extension "x-data-threescale-name": "user_keys" the auto-fill for user_key doesn't work from both admin portal and developer portal active docs   Expected result: The auto-fill should work for 2.0.    Documentation: https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.6/html/using_the_developer_portal/create-activedocs-spec   I think the migration from swagger > open API broke the extension.

      "x-data-threescale-name": "user_keys" auto-fill for active docs version 2.0 is broken

              Unassigned Unassigned
              vbhalera@redhat.com Vinay Bhalerao (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: