Tulir Asokan

We need to wait for decisions on #325 before continuing with further Space work.

There are currently two [`message`](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) listeners. The Space auth listener is at [space.js#L51-L56](https://github.com/apinf/openapi-designer/blob/a7ae20b91677238a4273f0f3dbfeac63a7131ff6/src/space.js#L51-L56) and the Swagger receiver is at [app.js#L106-L114](https://github.com/apinf/openapi-designer/blob/master/src/app.js#L106-L114). The remote file handling should probably be added to the...

Could you elaborate this a bit? I'm pretty sure we can trust the YAML library, and validating it with yet another library is just pointless. If you mean that some...

Changing this from within OpenAPI designer would be quite difficult. OpenAPI designer currently has no idea about the state of the wrapper, so those different instances are actually all the...

Fields that need info texts (based on previously opened issues): * Headers, examples, tags, consumes and produces under Paths * Consumes and produces (global) * Host field * License and...

We should look through the form and see what is still needed now that we have validation and placeholders.

We should probably wait for apinf/platform#2690 and see if we can use a similar CLA.

@bajiat I think the APInf platform integration problem is #327. URL parameters (actually client-side URL hashes, since designer doesn't have a webserver backend) that load specific APIs are probably more...

For sharing documents, I think we should just have an URL hash with the information needed to fetch the correct document from Space rather than the full URL. Though we'll...

I guess we can do that too, but it'll probably require escaping if we want IE/Edge compatibility