Express 3 compatibility #77

Closed
jedwood opened this Issue Mar 28, 2013 · 4 comments

Comments

Projects
None yet
3 participants
Contributor

jedwood commented Mar 28, 2013

I just made the necessary changes in my local modified version. If nobody else is already working on this, I'd be glad to submit a pull request.

I'd love a copy of this if you don't mind sharing.

I'm running express 3 and was looking at either this or swagger. I'm torn between the coupling of the code to docs in swagger that means it will never get out of date and the iodocs way which means an element of diligence in keeping docs updated but not having to change much of my api code to get it working.

If there is a load of effort to get iodocs working, then I may as well just go the swagger route so if you have a patch to shortcut this, then it would be a great help.

Contributor

jedwood commented May 23, 2013

I won't be able to get to this until mid-June, but will submit a pull
request then.

On Mon, May 20, 2013 at 4:35 AM, Jez McKinley notifications@github.comwrote:

I'd love a copy of this if you don't mind sharing.

I'm running express 3 and was looking at either this or swagger. I'm torn
between the coupling of the code to docs in swagger that means it will
never get out of date and the iodocs way which means an element of
diligence in keeping docs updated but not having to change much of my api
code to get it working.

If there is a load of effort to get iodocs working, then I may as well
just go the swagger route so if you have a patch to shortcut this, then it
would be a great help.


Reply to this email directly or view it on GitHubhttps://github.com/mashery/iodocs/issues/77#issuecomment-18141239
.

Thanks for letting me know. I will probably just use swagger as I was
leaning towards that anyway and I need to get a recommendation out
before mid-June. Will still take a look at what you have when you
release it though.

Cheers,
Jez.

On 23/05/13 21:16, Jed Wood wrote:

I won't be able to get to this until mid-June, but will submit a pull
request then.

On Mon, May 20, 2013 at 4:35 AM, Jez McKinley
notifications@github.comwrote:

I'd love a copy of this if you don't mind sharing.

I'm running express 3 and was looking at either this or swagger. I'm
torn
between the coupling of the code to docs in swagger that means it will
never get out of date and the iodocs way which means an element of
diligence in keeping docs updated but not having to change much of my
api
code to get it working.

If there is a load of effort to get iodocs working, then I may as well
just go the swagger route so if you have a patch to shortcut this,
then it
would be a great help.


Reply to this email directly or view it on
GitHubhttps://github.com/mashery/iodocs/issues/77#issuecomment-18141239
.


Reply to this email directly or view it on GitHub
#77 (comment).

Contributor

alexadkins commented Jul 1, 2013

Hey Jed, did you manage any progress on the express 3 compatibility? I would love to have a look at what you did as I'm trying to do the same thing myself.

Thanks!

@mansilladev mansilladev closed this in #97 Jul 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment