Make switching back and forth between Laravel and YaLinqo as seamless as possible. Use Collection::macro('linq', function) to extend Laravel. The cost of switching should be next to zero.
Investigate whether it's better idea to do that integration within a separate package or to add Laravel as a suggest in the package info for Composer.
Add more information on Laravel implementation to ReadMe. Specifically investigate how thoroughly and consistently keys are handled in Laravel collections.
Port useful and relevant methods from Laravel collections to YaLinqo. There's a lot of non-FP and non-pure rubbish with tons of SQL-isms, but some methods seem useful. If they're in Laravel, it's a good sign someone actually uses them (which can't be said about a lot of MoreLinq-like libraries). If there's a significant number of methods to port, split that into a separate issue.
Make switching back and forth between Laravel and YaLinqo as seamless as possible. Use
Collection::macro('linq', function)to extend Laravel. The cost of switching should be next to zero.Investigate whether it's better idea to do that integration within a separate package or to add Laravel as a
suggestin the package info for Composer.Add more information on Laravel implementation to ReadMe. Specifically investigate how thoroughly and consistently keys are handled in Laravel collections.
Port useful and relevant methods from Laravel collections to YaLinqo. There's a lot of non-FP and non-pure rubbish with tons of SQL-isms, but some methods seem useful. If they're in Laravel, it's a good sign someone actually uses them (which can't be said about a lot of MoreLinq-like libraries). If there's a significant number of methods to port, split that into a separate issue.
macromethod for extensibility