Magento 2.x Feature Requests and Improvements

I think we can divide Repository interfaces into multiple interfaces.so Extension providers don't need to provide implementation for all methods in interfaces. interface CustomerRepositorySaveInterface { /** * Create or update a customer. * * @param \Magento\Customer\Api\Data\CustomerInterface $customer * @param string $passwordHash * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\InputException If bad input is provided * @throws \Magento\Framework\Exception\State\InputMismatchException If the provided email is already used * @throws \Magento\Framework\Exception\LocalizedException */ public function save(\Magento\Customer\Api\Data\CustomerInterface $customer, $passwordHash = null); } interface CustomerRepositoryGetInterface { /** * Retrieve customer. * * @param string $email * @param int|null $websiteId * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\NoSuchEntityException If customer with the specified email does not exist. * @throws \Magento\Framework\Exception\LocalizedException */ public function get($email, $websiteId = null); /** * Get customer by customer ID. * * @param int $customerId * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\NoSuchEntityException If customer with the specified ID does not exist. * @throws \Magento\Framework\Exception\LocalizedException */ public function getById($customerId); /** * Retrieve customers which match a specified criteria. * * This call returns an array of objects, but detailed information about each object’s attributes might not be * included. See http://devdocs.magento.com/codelinks/attributes.html#CustomerRepositoryInterface to determine * which call to use to get detailed information about all attributes for an object. * * @param \Magento\Framework\Api\SearchCriteriaInterface $searchCriteria * @return \Magento\Customer\Api\Data\CustomerSearchResultsInterface * @throws \Magento\Framework\Exception\LocalizedException */ public function getList(\Magento\Framework\Api\SearchCriteriaInterface $searchCriteria); } interface CustomerRepositoryDeleteInterface { /** * Delete customer. * * @param \Magento\Customer\Api\Data\CustomerInterface $customer * @return bool true on success * @throws \Magento\Framework\Exception\LocalizedException */ public function delete(\Magento\Customer\Api\Data\CustomerInterface $customer); /** * Delete customer by ID. * * @param int $customerId * @return bool true on success * @throws \Magento\Framework\Exception\NoSuchEntityException * @throws \Magento\Framework\Exception\LocalizedException */ public function deleteById($customerId); } class CustomerRepository implements \Magento\Customer\Api\CustomerRepositorySaveInterface,\Magento\Customer\Api\CustomerRepositoryGetInterface,\Magento\Customer\Api\CustomerRepositoryDeleteInterface { }   ... View more

Magento 2 REST API get website_ids for product       Please provide additional GET REST API method on catalogProductWebsiteLinkRepositoryV1 to allow us to retrieve the website_ids for an sku. Or instead include the website_ids for an sku in catalogProductRepositoryV1 get /V1/products/{sku} ... View more

Hi,   I've see as of April 7, 2017 that Magento is rolling out a B2B Cloud for the Enterprise edition. I wonder if this is being considered, or some iteration, for the Community edition? I think this would be a great addition. ... View more

Currently the rest API doesn't send a websiteId attribute when you request a product.This would be really usefull for developers. ... View more

Mag V2 is missing the magentoInfo method that is available in Mag V1 APIs. Please add this to Mag V2 REST and SOAP APIs. It is necessary for feature validation when writing third party integrations. ... View more

While there are multiple threats a modern Magento application faces, one of the weakest from a security standpoint is the ability to run arbitrary commands without application level authentication via the command line. It seems to me the bin/magento command should require a user to be authenticated with the Magento application prior to execution of a command for a fully installed system. Whether that is achieved via user/pass or other method is up for discussion, just as long as the CLI was treated similarly to the web from an authentication point of view.   I understand that there are many ways to discount the need for such a feature, but given the power of the bin/magento command (and n98-magerun2) it seems prudent to authenticate (and log) actions.   This might be enforced at the framework / API level in order to help shell / CLI commands and n98-magerun inherit the same security stance.   Adding additional devdocs / publishing best practices on security hardening a Magento installation would also be nice to see.   Thank you for listening, Hardy Johnson   Technical Lead Copious, Inc.   hardyj@copiousinc.com ... View more

Problem is when thirdparty system wanted to update product's inventory then they require to send API call to update each products. So it calls cache flush method everytime that uses too much memory if thirdparty wanted to update 100o skus.   So I would suggest if have API call to update stock inventory which accepts skus in batch then it saves CPU memory. ... View more

Hi, We are using Live Search on Adobe Commerce 2.4.7. Right now the merchandizing rules are really limitative in terms of how we can manually add rules to sort products in a PLP or a Search Result page. We can only Boost / Bury / Pin / Hide a product by SKU, which is not really useful and really time consuming when we need to merchandize large catalogs. Would it be possible to add a ruling system according to product attributes ? For example a rule that would allow us to Boost product that have the color = red ? Let us know, Francis ... View more

Currently the API only allows to import special_price by "Scheduled Change". We would prefer a straight import of special_price value on store level (due to currencies for different countries). Because we handle price and special price in same table a convenient solution would be to pass special_price via API with base-prices just as one additional payload parameter: E.g. {   "prices": [     {       "price": 7,       "special_price": 0.7,       "store_id": 7,       "sku": "N4304700",       "extension_attributes": { }     },     {       "price": 9,       "special_price": 0.9,       "store_id": 9,       "sku": "N4304700",       "extension_attributes": { }     }   ] } ... View more

It will grateful for creating Websites, Stores and StoreViews using Rest APIs ... View more

For Example, we have below SKU's. DZ5321, DZ5321-EC, DZ5321-60, DZ5321-SC When I search keyword 5321 in the search box I need above all SKUs in the result. If we search the DZ then also I need above all SKUs in the result. For another example, "simpleproduct" if we search with simple or product for every situation, we need simpleproduct as search result. In the below search graphQl. { products( search : "5321" sort : { position : ASC } pageSize : 100, currentPage : 1 ) { total_count items { sku name } } }   ... View more

For example, if we search for "fiter" it shows us results for "filter" in the response as expected but there's no messaging for "Did you mean?" or "showing results for filter"   Currently, there is nothing in the live search response indicating what it's showing results for when the customer mis-types or it is showing results due to a fuzzy match.  Because of this, we can't show that it Didn't find results for "fiter" but it's showing you results for "filter" instead. ... View more

Hi,   As technically described here, Bearer and OAuth 1.0 integrations are deprecated in Magento 2.   In order to securely authentificate external APIs into Magento, it would be very useful to upgrade the Integrations extension in Magento 2 core. The topic is "Ready for grooming" since Dec. 9, 2021.   Is there by any chance an expected timeline for this feature?   Thank you! ... View more

Would be great to add "Include in menu" filter option for this interface: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/category-list/#categoryfilterinput-object   If you are creating a menu using GraphQL - you might want to retrieve only categories that should be shown in the menu.   This core feature: https://docs.magento.com/user-guide/v2.3/catalog/category-create.html#step-2-complete-the-basic-information (point 2) However, it's not supported by the GraphQL interface.   Without such a filter you will receive all categories, including those which shouldn't be in the menu. ... View more

To fetch Customer wishlist data, Magento is providing graphql.  But there is no rest API implemented to fetch customer wishlist data via Rest API.  We would request Magento team to implement rest API to fetch customer wish list data include the patch in upcoming releases or provide a patch to include it in existing versions.   ... View more

In order to display customer data on pages cached in the full page cache (Varnish or built in), the Magento framework and Magento customer module provide a number of related tools that enable this feature. Some details are outlined in the official documentation found at http://devdocs.magento.com/guides/v2.1/config-guide/cache/cache-priv-priv.html   Creating such a dynamic section on a cached page requires the use of two interfaces:   * Magento\Customer\CustomerData\SectionPoolInterface * Magento\Customer\CustomerData\SectionSourceInterface   The interface Magento\Customer\CustomerData\SectionPoolInterface is only referenced in the configuration file etc/frontend/di.xml, but the interface Magento\Customer\CustomerData\SectionSourceInterface has to be implemented in a custom class.   These interfaces currently are not marked with the @api annotation. Please add this annotation so the feature can be used in custom modules.   This actually also extends to the JavaScript "classes" Magento_Customer/js/customer-data and Magento_Ui/js/lib/core/element/element (a.k.a uiElement). Please also mark these as stable so the feature can be used as described in the documentation. Thank you!   ... View more

In order to display customer data on pages cached in the full page cache (Varnish or built in), the Magento framework and Magento customer module provide a number of related tools that enable this feature. Some details are outlined in the official documentation found at http://devdocs.magento.com/guides/v2.1/config-guide/cache/cache-priv-priv.html   Creating such a dynamic section on a cached page requires the use of two interfaces:   * Magento\Customer\CustomerData\SectionPoolInterface * Magento\Customer\CustomerData\SectionSourceInterface   The interface Magento\Customer\CustomerData\SectionPoolInterface is only referenced in the configuration file etc/frontend/di.xml, but the interface Magento\Customer\CustomerData\SectionSourceInterface has to be implemented in a custom class.   These interfaces currently are not marked with the @api annotation. Please add this annotation so the feature can be used in custom modules.   This actually also extends to the JavaScript "classes" Magento_Customer/js/customer-data and Magento_Ui/js/lib/core/element/element (a.k.a uiElement). Please also mark these as stable so the feature can be used as described in the documentation. Thank you!   ... View more

In some custom modules the IP address of the current visitor is required (e.g. for GeoIp lookups or access control). The class \Magento\Framework\HTTP\PhpEnvironment\RemoteAddress provides this feature, however it is not marked as stable. In order to be able to use the class within third party modules, it would be nice to have a method that is blessed with the  @api annotation. ... View more

If Swagger definitions for all the Magento endpoints such as Orders and Sales available it would be easy for making integrations and could be very useful for developers ... View more