Support the ongoing development of Laravel.io →
posted 8 years ago
Packages
Last updated 1 year ago.
0

Check out this package: https://github.com/caffeinated/shinobi

The developer does what you are trying to do. Also, his coding practices are really good!

0

illuminate3 said:

Check out this package: https://github.com/caffeinated/shinobi

The developer does what you are trying to do. Also, his coding practices are really good!

Thank you for your link!

0

@shahid ,

Any fix for the Warning: Ambiguous class resolution issue ?

0

arunkumar339 said:

@shahid ,

Any fix for the Warning: Ambiguous class resolution issue ?

Actually if you will use Namespace with database migration files and moves to project folder. then "composer dump-autoload" will throws this warning because same name-spaces are used in two different places. If you will not assign name space with migrations files. then it will not throw this warning. for now i fixed in this way.

0

To put it another way, I resolved my own issue with this by removing this section from my composer.json:

"classmap": ["migrations"	]
Last updated 8 years ago.
0

@weotch - good call. Did this in my package's composer.json and it removed the warnings.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.