Aimeos

Aimeos doesn't use Eloquent for performance reasons and thus, the queries won't show up in the LaravelDebugBar. You can see the queries in the Aimeos Log panel (admin backend) if...

The SQL queries for fetching products are using the mshop_index_* tables and you should have a look for those.

Lighthouse-php requires Eloquent models which we don't use for performance reasons. Thus, the package isn't compatible with Aimeos if you don't implement models for the tables Aimeos is using. GraphQL...

Yes, for the admin backend we are already working on a GraphQL interface. We've already played around with graphql-php package (https://webonyx.github.io/graphql-php/) to test the best way for relations and filtering...

The used parameter names are not conforming to the Omnipay standard. Current: ``` $order = [ 'body' => 'The test order', 'out_trade_no' => date('YmdHis').mt_rand(1000, 9999), 'total_fee' => 1, //=0.01 'spbill_create_ip'...

We are not experts in what the Omnipay driver expects. If the usage guide (https://github.com/lokielse/omnipay-wechatpay#usage) doesn't help, you should dig into the code of the WechatPay driver to see what...

There's also a problem with the Laravel router when mapping route variables to method arguments: https://github.com/laravel/framework/issues/36997 @taylorotwell Is there any plan to support multi-lingual routes in future versions of Laravel?

The Doctrine collection API is completely frozen for years and there won't be any major improvements (even not in 2.0) due to the ecosystem and other Doctrine projects relying on...

Our objects have some convenient methods like `$detailProductItem->getRefItems( 'attribute', null, 'config' )` * attribute: domain * null: type * config: list type In this example, from a flat list of...

Yes, that was our first thought but it would require a view helper for every method that contains a parameter ... too much to be a suitable solution ... In...