routing-controllers-openapi *-extended*

[leonardlin]

This is amazing,
I've been waiting for a replacement because my CI tools to all christmas-tree on routing-controllers.

I am also using "routing-controllers-openapi" which has a peer dependency to routing-controllers@0.9

Are you interested to add these ecosystem libraries too?
I would help you update routing-controllers-openapi-extended to work with your routing-controllers-extended.

I guess a better name is "routing-controllers-extended-openapi"

[spicemc]

Glad you like it.

It's a great idea and "routing-controllers-openapi" is a great project.
Since my bandwidth is limited to handle additional projects we could ask the maintainer to add routing-controllers-extended as a peer dependency?
It seems to be abandoned too so we might be unlucky. Then i would fork and update it with your help. And yes "routing-controllers-extended-openapi" sounds good.

[leonardlin]

I placed the question: epiphone/routing-controllers-openapi#120

I wait what they say, otherwise we can fork it.

[spicemc]

👍

[leonardlin]

It's been a week, so I think the project is dead too.
Would you mind to fork it? I would get on updating it asap.

[spicemc]

Sure. It's forked now and i sent an invitation to you.

[leonardlin]

Thanks, on it.

[leonardlin]

@spicemc I think the https://github.com/spicemc/routing-controllers-extended-openapi is ready.

• tests pass
• sample updated and tested
• updated docu

I think next would be to setup publish to npm.
I have never done that and I might not have permissions for that, could I trouble you for that step?

Thanks Leo

[spicemc]

Sure, i`ll take care of this.
Yes, it's not possible to publish without my npm token.

[spicemc]

It's published as 4.0.0 because 1.0.0 already exists.