For API?

[shirshak55]

I guess there is namespacing on this spatie permissions package. How should we work this in API. As laravel supports Resources in laravel 5.5 the demo should not be hard for api? For Api are we going to duplicate soo much roles and permissions in tables?? Can we make demo for that also as in modern days there will be mobile app version of almost every website right?

[drbyte]

Adding a demo of the API Resource support in 5.5 is a good idea.
Willing to collaborate to put one together. Wanna help?

I'd like to address your namespacing question, but I think it's better handled over in the package repo itself, as it relates to the multiple guards feature. Do you mind posting this as an Issue over in the https://github.com/spatie/laravel-permission/issues/ repo?

[shirshak55]

Hi I am willing to collabrate . Yes I guess we need to discuss with freekmurze. I guess namespacing problem will be fixed on v3 of that package.

spatie/laravel-permission#479

[drbyte]

Great!

If you're okay with the demo leveraging what's already here in this demo, shall we just do it right here, using PRs?

I'll clone master into api as a working branch, and when we're satisfied it's complete we can merge into master.

[shirshak55]

Sure . We will work in api and we will leverage whats already here as it will maintain consistency

[drbyte]

Excellent.

[eternalBlast]

Is this role for api can be used now?