GautierDele
Repos
15
Followers
12
Following
10

Events

issue comment
Aggregate support: count, max, min, avg, sum

In my opinion we should add a new params "includesCount", "includesMax", etc and those counts should be directly added to the resources because you might want to count the number of children for each resource. The problem is: what if you want to add params to those avg / count / etc because you might want to filter what you include / etc ? This could be added in the direct close of "withCount" pretty easily ?

I don't think we can add this to the meta since this should be dynamic to each resource ?

Created at 3 hours ago

:bug: hmr was having trouble with docker

Created at 2 weeks ago
GautierDele create branch main
Created at 2 weeks ago
GautierDele create repository
Created at 2 weeks ago
issue comment
[v4] sort by graphql duplicating rows

We are nearly coming to a year of this issue, is this fixed by any other way right now or still there ?

Created at 3 weeks ago
issue comment
Aggregate support: count, max, min, avg, sum

Would be necessary for us :)

Created at 1 month ago
issue comment
filter on relation pivot

I did investigate but it would need much more time than i tought because the code isn't prepared for this.

If someone wants to take a look, i let this open.

FYI: needs to impact pivot action on: "filtering", "sorting" and "qualifyScopedFilterField"

Created at 1 month ago
issue comment
filter on relation pivot

I don't think this is related to nested queries since "relation" gives the whole string before the field and the check is strict to "pivot" so when you want to join "pivot.field" it works but when it is "relation.pivot.field" it doesn't.

I'll have a check on my spare time to implement this since it's required for us and would be really usefull for people.

Created at 2 months ago
issue comment
filter on relation pivot

I investigated and it seems like this isn't covered right now: image I this something you had in mind or not at all ?

Created at 2 months ago
opened issue
filter on relation pivot

Hello there,

On a Many To Many resource it's written that you can filter by pivot value but when you want to filter on a pivot of a relation it seems like it's not working:

{
    "filters": [
        {
            "field": "task_type_id",
            "operator": "=",
            "value": "2d1399a2-2e61-4af5-b2ff-7c0726141998"
        },
        {
            "type": "and",
            "nested": [
                {
                    "field": "customFields.id",
                    "operator": "=",
                    "value": "96c2d325-5980-42fd-8a05-25cb68b45557"
                },
                {
                    "field": "customFields.pivot.value",
                    "operator": "like",
                    "value": "%bb%"
                }
            ]
        }
    ]
}

Basically, Orion is trying to access the pivot relation on "customFields" model here. "pivot relation can not be found". Did we go on a not covered functioning ?

Thanks,

Created at 2 months ago
issue comment
:sparkles: nested filters

Thanks !

Created at 2 months ago

Revert ":sparkles: pagination documentation"

This reverts commit 9e12e70c569f7dd4099238a80f19354e9c599398.

Created at 2 months ago
:sparkles: nested filtering

@alexzarbn be aware that i added pagination documentation since it's not provided anywhere

Created at 2 months ago

:sparkles: pagination documentation

Created at 2 months ago
GautierDele create branch feature/pagination-from-query
Created at 2 months ago

:recycle: code cleaning

Created at 2 months ago
issue comment
:sparkles: nested filters

In order to avoid this breaking change, i did set default value to 1.

Created at 2 months ago

:sparkles: set max_nested_depth default value

Created at 2 months ago
issue comment
:sparkles: nested filters

Moving "max_nested_depth" to the search is a breaking change because Laravel won't merge it in the service provider. Be sure to add it in the release process and increase middle version.

Created at 2 months ago

:recycle: review requested

Created at 2 months ago
issue comment
:sparkles: nested filters

On my side it's working fine but test arn't passing, is it normal ? I can see it's on other place of the app

Created at 2 months ago

:bug: disallow field on nested field

Created at 2 months ago

:bug: wrong rule

Created at 2 months ago

:white_check_mark: :bug: condition on validator wasn't correct

Created at 2 months ago

:arrow_down: downgraded php 7.4 to 7.3

Created at 2 months ago
issue comment
:sparkles: nested filters

@alexzarbn I refer mostly to a security / performance issue. Where the front could add a lot of nested filters and probably slow really much the application if he adds thousands of nested filters since the nested filters are theoretically infinite.

Created at 2 months ago
pull request opened
:sparkles: nested filtering

relates https://github.com/tailflow/laravel-orion/pull/163

Created at 2 months ago