Ideas

Today we can get children for a specific page, but to build some kind of navigation in a sidebar we have to make a very weird nested children query. It would therefore be nice to add the ability to get all descendants of a page, with maybe a depth...

We lack the ability to build a listing of pages using the page search and the children on pages. For example to build a news list where we want to have filters on different "tags" for a news list. Also a way to sort based on publish or created dat...

We have the need to be able to get all relations for a product without specifying each relation in the gql query. We need to be able to fetch relationsships dynamically on the product page.

The ability to filter out products that doesn't have a price would be a good feature. As today in the graphql api products without a price in the current assortment gets returned. Which could be good for some scenarios, but for most scenarios we o...

Add sortCriteria for PageSearchResultContext like there is for CategorySearchResultContext and ProductSearchResultContext.

Paging for large productlists When working with customers with a lot of products the listing takes quite a loot of time to load and filter.Would be nice to instead have a pager functionality and an optional to select pagesize or all where default ...

As a logged in user/customer - add the ability to log-out. (Note: If you change a logged in users Role operations they are not applied until you remove the cookie and log-in again)

Often you need to fetch one or more entities other than the one i the current URL-context, for example if you have a list of article numbers in a cookie to display recently visited products or article numbers saved in state. Currently you cannot u...

In Litium 8 you can't see which channels a variant is published on in a single view, you have to open up all markets using the "Select variants"'popup and find the variant to see if it is published there. This makes publishing very tedious if you ...

Using the React Accelerator, you cannot change the behavior of search scoring on fields. For example you would like to disable fuzzy search on article number and score these higher than hits in body text on a product. With the MVC Accelerator you ...