You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming out of discussions in meeting and #271 and #285 , it seems like the topic of sorting and filter in GraphQL (like for solving the issue of the shelf's sub nav) should be moved to its own issue.
Details
There are a couple options under consideration for achieving this
Queries
The enhancement here would be to allow users to request the order of results instead of having to do it themselves (somewhat negating the value of querying for the data in the first place).
Declarative
One option is to be able to do something like this
query {
navigation{
label,
'page-a',
'page-c',
'page-b'
link
}
}
Params
Another way would be to have it done through the client / GraphQL
But also like in #274, this would require everything to be 100% percent transparent. In #285, one issue is that the specific logic to the user (e.g. menu) is too specific to the implementation of the Greenwood website, and not really useful or should be hardcoded into any public to users (e.g resolvers, queries, etc).
The text was updated successfully, but these errors were encountered:
In #285, one issue is that the specific logic to the user (e.g. menu) is too specific to the implementation of the Greenwood website
I disagree, the logic is for any menu, on any website, and could be utilised for footers, side menus, or navigation. The example from that PR is using greenwood website, but nothing in the logic is specific to greenwood website. Menu is just one query example. This is further explained in #291
Type of Change
Summary
Coming out of discussions in meeting and #271 and #285 , it seems like the topic of sorting and filter in GraphQL (like for solving the issue of the shelf's sub nav) should be moved to its own issue.
Details
There are a couple options under consideration for achieving this
Queries
The enhancement here would be to allow users to request the order of results instead of having to do it themselves (somewhat negating the value of querying for the data in the first place).
Declarative
One option is to be able to do something like this
Params
Another way would be to have it done through the client / GraphQL
Front Matter
The front matter approach would be similar to what is being requested in #274 , in that menu configuration could be added as front matter, e.g.
And then queried.
But also like in #274, this would require everything to be 100% percent transparent. In #285, one issue is that the specific logic to the user (e.g.
menu
) is too specific to the implementation of the Greenwood website, and not really useful or should be hardcoded into any public to users (e.g resolvers, queries, etc).The text was updated successfully, but these errors were encountered: