You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing a new API from a file, the correct file type is not being auto-selected and it defaults to JSON. This causes the user to manually go and select the file type from the dropdown list in the UI, in order to fix the JSON validation issues and see the correct syntax highlighting.
To Reproduce
Go to the APIs Tab in the main app
Click on the Create an API button if it's your first API or use the + New API button if it's not
Import a new non-JSON schema using either of the import flows (browse for the file/drag and drop)
Expected behaviour
When a file is either Imported, the file type should be auto-selected from the list of options (If the file type is supported/content is valid).
Screenshots/gifs
The gif below shows the current in-app behaviour:
App information:
App Type Native App
Postman Version 7.3.4
OS: macOS Mojave 10.14.5
Additional context
This code can be saved as a .yml file to test the issue:
openapi: 3.0.0info:
title: Sample APIdescription: Optional multiline or single-line description in [CommonMark](http://commonmark.org/help/) or HTML.version: 0.1.9servers:
- url: http://api.example.com/v1description: Optional server description, e.g. Main (production) server
- url: http://staging-api.example.comdescription: Optional server description, e.g. Internal staging server for testingpaths:
/users:
get:
summary: Returns a list of users.description: Optional extended description in CommonMark or HTML.responses:
'200': # status codedescription: A JSON array of user namescontent:
application/json:
schema:
type: arrayitems:
type: string
The text was updated successfully, but these errors were encountered:
@sankalp0o I need to reconfirm that this is still an issue as there has been a lot of work down with the import flow recently. Do you know if this was picked up as part of the work?
Describe the bug
When importing a new API from a file, the correct
file type
is not being auto-selected and it defaults to JSON. This causes the user to manually go and select the file type from the dropdown list in the UI, in order to fix the JSON validation issues and see the correct syntax highlighting.To Reproduce
APIs
Tab in the main appCreate an API
button if it's your first API or use the+ New API
button if it's notnon-JSON
schema using either of the import flows (browse for the file/drag and drop)Expected behaviour
When a file is either Imported, the file type should be auto-selected from the list of options (If the file type is supported/content is valid).
Screenshots/gifs
The gif below shows the current in-app behaviour:
App information:
Additional context
This code can be saved as a
.yml
file to test the issue:The text was updated successfully, but these errors were encountered: