statsable

[ThanhSonITNIC]

When we want to extend filters and interactions in resource with stats data

PostResource

public function stats(\Illuminate\Contracts\Database\Eloquent\Builder $query): array
{
    return [
        'posts_has_approved_comments' => $query->whereHas('comments', fn($q) => $q->where('approved', true))->count(),
        'posts_has_worse_comments' => $query->whereHas('comments', fn($q) => $q->where('star', '<', 3))->count(),
        'published' => $query->where('published', true)->count(),
    ];
}

Request [POST] api/posts/search

{
  "search": {
    "stats": true,
    ...
  }
}

Response

{
    "current_page": 1,
    "data": [...],
    "from": 1,
    "last_page": 1,
    "per_page": 50,
    "to": 10,
    "total": 10,
    "meta": {
        "stats": {
            "posts_has_approved_comments": 5,
            "posts_has_worse_comments": 2,
            "published": 9,
        }
    }
}

[ThanhSonITNIC]

https://github.com/Lomkit/laravel-rest-api/issues/105 aggregates can't be complex and multiple response keys in a relation

[GautierDele]

Could you please add unit tests, i'm quite sur when you'll have problems with your example because the query is manipulated multiple time and is immutable

[ThanhSonITNIC]

Another example, we need stats of orders:

• Sum of debit transactions
• Sum of payment transactions
• Total of return items

I have some ways:

• Store fields in database: this way is not perfect when stats data difference by seller and customer
• use "aggregates": aggregates can't be multiple response [relation, type, field] in relation transactions

  "aggregates": [
  {
  "relation": "transactions",
  "type": "sum",
  "field": "amount",
  "filters": [
    {"field": "type", "value": "debit"}
  ]
  },
  {
  "relation": "transactions",
  "type": "sum",
  "field": "amount",
  "filters": [
    {"field": "type", "value": "payment"}
  ]
  },
  {
  "relation": "items",
  "type": "sum",
  "field": "quantity_return"
  }
  ],

• Create custom api: [GET]\api\orders\stats this api not extend search and interactions from this package

[ThanhSonITNIC]

Could you please add unit tests, i'm quite sur when you'll have problems with your example because the query is manipulated multiple time and is immutable

unit test better by your

[ThanhSonITNIC]

@GautierDele please review, it take 3 days

[GautierDele]

I gave you the problem, i'm not able to handle this for now