Dimitrios Dedoussis

Thanks for putting the issue together! This is indeed a glitch of the existing spec (`2.0.0`) and I think the root cause of the glitch is the `url` field of...

Instead of dropping the `url` field and introducing new fields (for the different parts of the `url`), I would suggest the inverse approach: Drop the `protocol` field and enforce the...

> Enforcing the URL to be always absolute would go against our plans to support any kind of APIs in the future (REST too). I see. In that case, I...

Happy to champion this RFC by the way. Will be putting together a Stage 1 proposal.

Get exactly the same error when I try to build/debug a Java project of mine. After proceeding, the project seems to have been built fine. IntelliJ is also not throwing...

Hi @alex-zywicki, apologies for the delay. This is indeed a bug, but the fix is a bit more complex than the one you propose. Will look into raising a PR.

Have released version `0.8.3` that fixes this.

@alex-zywicki Would it be possible to confirm that the new version fixes the issue you encountered? If so, this thread can be closed I guess.

@alex-zywicki I think it would be simpler to approach this problem from another POV. As in: keep the core of asynction aligned with Flask-SocketIO, which does not have multi API...

> @dedoussis I'm fine with that. That was my original thought, but you seemed averse to that initially when you said 'I think merging of spec files is a recipe...