architecture
architecture copied to clipboard
A place where Magento architectural discussions happen
## Problem Current schema for custom attributes doesn't support attributes that can have multiple values (checkbox, multiselect). ## Solution ## Requested Reviewers
## Problem Cart and Negotiable quote share common fields and sometimes they're used interchangeably ## Solution Create an interface for Quote ## Requested Reviewers
## Problem Products query doesn't contain reference to wishlist, it takes a round trip to render a PDP page dropdown to what wishlists are assgined to the product ## Solution...
## Problem There's no way to grab an object by ID. We need a global way to do this and graphql spec is the answer. ## Solution Add a node...
## Problem By deprecating urlResolver we need to make sure that we can get the same data from Routable Interface It turns out that we're missing some basic functionality that...
## Problem Customer Reorder Schema needs to update id with UID changes. ## Solution With consistency throughout the graphql schema, we have replaced the Id field with Uid. ## Requested...
## Problem - We're missing lots of fields to place orders, this attends to add them back. - I've added new StoreConfig fields to provide the information which fields should...
[Rendered Document](/magento/architecture/blob/updates-to-extensibility-doc/design-documents/graph-ql/extensibility.md) I noticed the extensibility document was missing some content while I was updating it with proposed solution from #400. This PR contains changes to address #400 and some...
> ## Problem Schema has a lot of fields named id which doesn't align with the new naming convention of GraphQL > ## Solution Updating all id fields to `uid`...
## Problem To build proper customer address forms, we need to have some additional information. ## Solution I've split this PR in two commits, the first is a copy of...