Magento GraphQL Community, 31 Oct 2019

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: GraphQL: Bi-weekly Community Meeting 10/31/2019

Description

Agenda:

- Customer orders schema and backlog
- Fixed issue with several errors per one GraphQL request
- Approved wishlist schema
- Customer wishlist functionality
- Use cases for adding bundle product to cart

A

Which you buy weekly Raquel community medium, our today's agenda is contains following items. I will start from from some line items I would like to present them. I would like to talk about. Actually, how is the connection? How how do you hear me because I believe there is too much noise around you I hear.

B

You fine, okay,.

A

That's awesome, so I would like to start from the first item its customer order schema recently.

A

The schema for customer orders was approved by architecture team, and the idea behind behind this is that, right now, with the current approach, schema allows fetching on the simple order details and it doesn't provide possibility to fetch order details by a number. So so the proposal is to add orders field to the customer type which will contain the list of customer orders with the information like status number will contain items, invoices reference, information, shipping and payment methods.

A

This, based on this schema I created I created tasks. Here is this list, so the the first one from the bottom is order details by order number separately health ticket for invoices, shipping, details, refunds and order items about all the details. It's like pretty pretty straightforward.

A

If somebody is interested in working on this, just like assign this issue to yourself in case, if you will have any new any questions that feel free to ask me directly or in the graph yells our channel.

A

This is the first item. Maybe maybe you have some questions about this if, if no questions I will proceed with with next item, the next is recently we fixed issue with several errors per one graph killer request how it was previously I think if you did some validation logic, for example, for shipping addresses.

A

Even if the response, the response contains array of errors always on the one error was like return previously and for some cases like, even if multiple errors cure during the some kind of validation, it was just included into message and displayed as assisting right now.

A

This issue is fixed, and here is the good example when we want to set shipping address on the card, and we have in address, have missing few missile required fields like phone number and postcode, and for this mutation we will get array of errors with secure element that phone is Mason and postcode is Mason.

A

This is I believe this is like important fix, because for any like future implementation and case, if you need to make some input, validation, you can use I will show you can use a.

A

Graphical input exception, so we added here at error method and in order to to create multiple errors, this method should be used. I will show you example said the link, for example, this one said: shipping address or card. We get array of errors by : other date method, and then we iterate through through the array of errors and and add this error geography of input exception which implements the aggregate interface in this case.

A

Instead of the important messages we will be able to display to display all all errors that that occurred during during some kind of validation.

A

Yeah. That's that probably it about errors may be maybe some questions, but.

A

It's no questions.

A

The last topic- yeah I, wanted to say about approved, wishlist schema I will show it to you.

A

A

You it's ujin here on the corner: isn't: okay, maybe I will show his his ticket as well, because it's related to wishlist. So the current implementation is that for customer wishlist we have separate quality, but it was decided to market is deprecated and remove this list under the customer type.

A

It like. We assume that the wishlist always exists for customers. So under the hood, when when we will make a call on customer type, we will always get the wishlist in response in commerce addition, we have multiple wishlist functionality, so it was decided to for commerce purposes, create, wish lists additional implemented additional field which will return reign of wishlist and extend in commerce. Addition extend.

A

Wishlist filled with ID argument in order to return data for for specific revision list by ad.

A

We also in the proposal it was decided to add for commerce functionality at mutation, leak rate, wishlist or demolish list, because it's actual width only in cases when, when you want to work with multiple wish lists and some mutation like add products to wish list removal they product. It's.

A

This functionality right now has dependency on single cart, single mutation for egg, in front of the cart, because it will use absolutely the same approach so the same way how we want to add products to card the same approach for before adding products list and.

A

The this part about customer wishlist is already implemented and for other mutations we have created tickets. So if, if you are interesting, just like have a look on the board, maybe you'll find something for for you and on add products to wishlist. Yaroslav is working right now.

A

Yeah, probably that's it from me. Maybe maybe some questions.

A

Okay, since virgin is not here, how much could you please proceed with test cases? The use cases for bundled products.

B

Yes, of course, hello, everyone today I will show the pull request which tries to implement the feature of adding bundle products to the cart. It's this pull request is quite old. So, let's begin I'll show my screen. I.

B

Hope you are seeing my screen. Do yes, okay, so I installed magenta with sampled data. I will use this predefined customer and we will try to add bundle product to the cart.

B

So here you see the skew of the product that I am going to add to cart.

B

I'll already have a customer token and card Oh.

B

As you see, it's already exist.

B

Here here you see the details of the bundled product. Well, let's see in this step and at what we want next up, so we have option ID, one with three radio options and option I did to which also has a series of fields or selections.

B

So we can add multiple at the same time, I.

B

Think I had a mistake.

B

So the first one will be option: one with ID 1, 2, & 3.

B

And the second one.

B

Let's see how it works now we haven't selected all required fields, so the first is required second and sit and also the fourth, let's add more.

B

I'm looking for the option, ID of this set option, it's 5.

B

Let's see now so we added products, it's not easy to see how it looks here we can log in as a customer and Caeser.

B

And so you see that we successfully added the product to the card, but there is one little problem. As you see, we added multiple choice for the first option and I think it should be. It should not be allowed to do this because when we open this product as a customer.

B

We have only one choice, but now we can use graph Yelp to add even multiple items. One request, though, that's all from me thank you for your attention. Thank.

A

You it turned out that I've talked a lot, but I didn't share my screen, so probably I need to fix this a little bit and just show items that that's hot I was talking about. Didn't shout about my account and order details here is the list of issues don't issue?

A

Am I sharing my screen right now? Yeah. Okay, so did you use your time sharing right now and each each show contains link to the approved architectural document about all the details. So you can have a look on this and about errors.

A

What I wanted to show is the example of how this validation will look like, for example, for addresses, and if some fields are missing right now it will be a range of errors in comparison with Harvard was before it was just array of one element by our messages: well imported into single string and yeah about wishlist its.

A

Approved document, so you can go to the architecture repo and get familiar with this proposal. Yeah. Sorry about that.

A

Yeah, probably that's it for today. Thus anyone have anything to add.

A

Okay, so thank you see you in two weeks, thanks bye thanks.

B