Koa2 repo contrib

[ctataryn]

Hi there, in response to #170 I forked a new repo off of koa2-oauth-server and modified it to use @node-oauth/oauth2-server. @jankapunkt would you like to create a new repo for it under the node-oauth org like you have for the express-oauth-server?

The forked repo with the changes can be found here:

https://github.com/ctataryn/koa2-oauth-server

[jankapunkt]

@ctataryn thank you for this! I will check it out and get back to you. Are you willing to keep maintaining it with us together, in case it gets merged into this org?

[jankapunkt]

Coming back to you, let me summarize my thoughts. First of all, thank you very much for stepping up! This is a great move forward, if we finally add koa support.

Here are my technical thoughts:

• let's create a new repo and merge into it as it is right now
• add test coverage to reach 100% coverage (me, should be feasible for this repo)
• in the next step I will setup a GitHub CI pipeline (me)
• then we would have to upgrade the code to ES6 (or even better: TypeScript, if you're proficient) and fully async/await
• have a review from everyone, and if passing, releasing the new major version 3.0.0
• post publishing, updating the README and the docs on the main @node-oauth/oauth2-server repo (where Koa is mentioned)
• finally, adding a Koa example to the examples repo

Any thoughts on this?

[ctataryn]

Sounds good 👍 If you have suggestions on how to get coverage up, let me know (i.e. tools that identify the coverage gaps, etc...) I know you're going to take on the task, but always like to learn how people do things.

[jankapunkt]

@ctataryn this repository contains a full test setup that also runs coverage:

https://github.com/node-oauth/node-oauth2-server/blob/master/package.json#L49C1-L49C136

[jankapunkt]

@ctataryn I'd like this not be forgotten. How do we want to move on here?

[ctataryn]

@jankapunkt for sure, let me circle back. I kinda made the changes I needed to get me past a certain point in my project and I've been living off that version in my fork and then got busy. I'll have some time next week to look at the above and hopefully get this all up and running with tests.