Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any future development planned? #2

Open
mos-ie opened this issue Dec 5, 2018 · 3 comments
Open

Any future development planned? #2

mos-ie opened this issue Dec 5, 2018 · 3 comments

Comments

@mos-ie
Copy link

mos-ie commented Dec 5, 2018

Really like this project - have you a road map?

@mmacneil
Copy link
Owner

Thanks and sorry for the extremely late reply. I had intended on making some improvements but as always other priorities took my time. Have you used this project in your own work? Are there things you'd like to see added, fixed or improved?

@mos-ie
Copy link
Author

mos-ie commented Aug 20, 2019

No worries. Using it in a project that will be going live soon - https://phynda.app/

It would be great to see a client implementation that consumes the API and makes use of the refresh tokens - this was the one part that I couldn't get working in my Ionic 4/Angular 7 app.

There would probably be a lot of work in this, but a VS plugin to scaffold all presenters, validators, use cases etc. for each use case would ultimately save a lot time.

@neutrin0x
Copy link

hey Mark, thanks for sharing this starter project... It was really helpful.
I'm learning abouts API and net core and I'm just wondering if it's possible to do Role Based authorization with this approach, I've tried policy based, but I can't figure it out how it works.
Anyone has tried role based or policy based with this approach? Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants