Open niklaswolf opened 3 years ago
Hi @niklaswolf. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Golf. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
As per Magento docs customer_address_id is not added yet for CartAddressInterface which is existing behavior. Adding Feature Request label as this can be considered as Feature request but not bug.
As a developer I want to know the customer_address_id on a CartAddress so that I know if a customer has selected one of the customer addresses
mutation SetCustomerShippingAddressOnCart($cartId: String!, $customerAddressId: Int!) {
setShippingAddressesOnCart(
input: { cart_id: $cartId, shipping_addresses: [{ customer_address_id: $customerAddressId }] }
) {
cart {
id
__typename
shipping_addresses {
id
customer_address_id
}
billing_address {
id
customer_address_id
}
}
}
}
Current CartAddressInteface
Add these fields:
interface CartAddressInterface {
id: ID!
customer_address_id: ID @doc(description: "Reference to customer address")
}
If the CustomerAddress has implemented the uid
we'd like to have customer_address_uid
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x
, ^Area:.*
Once all required labels are present, please add Issue: Confirmed
label again.
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x
, ^Area:.*
Once all required labels are present, please add Issue: Confirmed
label again.
@cpartica this is a big problem.
@paales @cpartica - https://github.com/graycoreio/magento2-quote-graphql-aux
I've recently had a comment from @hnsr that I should write better code and is is very unclear, which I agree.
@hnsr We might be able to implement a local resolver for this in GraphCommerce and make @damienwebdev's package optional and move to a Magento native solution when it is implemented.
Hi @chernenm. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
As a developer I want to get the customer_address_id of cart addresses so that I can match them easily with the other addresses a customer has saved in his customer addresses. Right now you have to do basically a string compare with a combination of fields to get a match, which in fact doesn't have to be a match because you can create different customer addresses with exactly the same values.
Added info from @paales As a developer I want to know the customer_address_id on a CartAddress so that I know if a customer has selected one of the customer addresses
Schema
Current CartAddressInteface
Add these fields:
If the CustomerAddress has implemented the
uid
we'd like to havecustomer_address_uid
AC
customer_address_id
field is added toCartAddressInterface