asyncapi / studio

Visually design your AsyncAPI files and event-driven architecture.
https://studio.asyncapi.com
Apache License 2.0
169 stars 100 forks source link

`Import from URL` should not use custom fetching but `parseFromUrl` #392

Closed derberg closed 1 year ago

derberg commented 2 years ago

Reason/Context

I'm not suggesting a solution. We can still use parse function I think. We just need to pass to dereferencing library option that will set proper base URL for dereferencing, so relative $ref resolution works.

In other words: I want to import https://raw.githubusercontent.com/asyncapi/spec/master/examples/social-media/public-api/asyncapi.yaml in Studio and have it work and $ref from there resolved against `https://raw.githubusercontent.com/asyncapi/spec/master/examples/social-media/common/messages.yaml#/commentLiked

Probably, next to info that file is in locaStorage we need to display info that a base URL is applied to dereferencing and someone can edit the URL or remove it

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart: