Skip to content

[GraphQL] Missing mutation to share wishlist via email #39870

Open
@lintots

Description

@lintots

Preconditions and environment

Magento 2.4.x with Wishlist GraphQL enabled.
Currently, Magento's GraphQL API allows creating, updating, and deleting wishlists and wishlist items. However, there is no available GraphQL mutation to share a wishlist via email, which is a core feature available in Magento’s storefront (Luma) via standard HTTP POST.

Steps to reproduce

  • Install Magento 2.4.x with Wishlist GraphQL module enabled (Magento_WishlistGraphQl is core since 2.4.0).
  • Create a Customer and Login using Customer Token via GraphQL.
  • Create a Wishlist and add products using GraphQL mutations:
    1. createWishlist
    2. addProductsToWishlist
  • Try to find a GraphQL mutation to share the wishlist via email.

Observe that:
No such mutation (shareWishlist) exists in the GraphQL schema.
Sharing is only possible via the Magento frontend (wishlist/shared/send/) using HTTP POST (controller-based).

Expected result

A GraphQL mutation like shareWishlist should be available. It should accept parameters like:

  • wishlist_id or wishlist_uid
  • emails (list of email addresses)
  • message (optional)
    Expected mutation
    mutation {
    shareWishlist(
    input: {
    wishlist_uid: "xxx",
    emails: ["test@example.com"],
    message: "Check out my wishlist!"
    }
    ) {
    success
    }
    }

Actual result

No such mutation is available. Sharing a wishlist is only possible via traditional Magento PHP controllers (wishlist/shared/send/ route).
Impact:

  • Cannot implement full wishlist features in PWA or headless applications.
  • Breaks UX consistency between frontend and headless apps.
  • Forces developers to build workarounds outside GraphQL standards.

Additional information

Suggestion:
Introduce a shareWishlist mutation as part of Magento_WishlistGraphQl module.

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

Metadata

Metadata

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions