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 using asyncapi new -e any-example to generate a new asyncapi specification file based on an example file after providing a different file name than the example file and selecting yes to open it in studio cli fails to do it.
Example
using anyof-asyncapi.yml example file and providing it a different name as different than the example file name and selecting yes to open it in studio we get SpecificationFileError: File differnt does not exist. even after the file has been created.
but if the same file name is provided the studio opens perfectly.
Expected behavior
Studio should open with the custom file name given by user.
Screenshots
How to Reproduce
Create an new file using asyncapi new -e anyof-asyncapi.yml
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Describe the bug.
When using
asyncapi new -e any-example
to generate a new asyncapi specification file based on an example file after providing a different file name than the example file and selectingyes
to open it in studio cli fails to do it.Example
using
anyof-asyncapi.yml
example file and providing it a different name asdifferent
than the example file name and selectingyes
to open it in studio we getSpecificationFileError: File differnt does not exist.
even after the file has been created.but if the same file name is provided the studio opens perfectly.
Expected behavior
Studio should open with the custom file name given by user.
Screenshots
How to Reproduce
asyncapi new -e anyof-asyncapi.yml
Specification Error
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: