-
Notifications
You must be signed in to change notification settings - Fork 29
magento-engcom/import-export-improvements#101 Remove sku autogeneration on new products, keep on duplication #119
Conversation
Thanks for the PR @pogster for me I think it would be fine to generate the sku on duplication. Feel free to reach out to me if you need help with the tests. |
0e3b985
to
cd3f085
Compare
ac1c426
to
91f0b53
Compare
…ed. Duplicate needs a SKU to be saved.
…and the constraint anymore this way. Test needs to be adjusted to result in expected error.
…U won't be changed by beforeSave anymore. Only a duplicated product will receive a changed SKU on its creation.
…th the same URL key to prevent 'SKU already exists' error.
5d376fb
to
2368e8f
Compare
Clean up the header of the class to fit with the static-tests.
On you branch we have the following testing scenario:
But on 2.3-develop we get the following on step 7:
My thought is that it should work as it does on 2.3-develop with a new product created with a unique sku and url. What do you think @pogster |
I'm sorry but I fail to reproduce that behaviour on my branch pogster:sku-uniqueness. I don't see a difference to the 2.3-develop behaviour and I don't get that error message. |
carstenpfeifer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. |
No update here as yet from the QA team but I have asked for further details for you. |
Looking at the code I can not imagine how the described behaviour should
occur. For me it sounds like it was tested on a wrong/incomplete/old
branch.
Am Fr., 16. Nov. 2018, 13:57 hat David Manners <[email protected]>
geschrieben:
… No update here as yet from the QA team but I have asked for further
details for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#119 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHPlIH3TeB_SO-WJlIRQT3Bsu2XDeCEHks5uvrYcgaJpZM4V5UnB>
.
|
Thanks for the information @VasylShvorak does that help you out @pogster? |
Per request from @dmanners I ran a few test scenarios: Testing scenarios: B) C) In line with @pogster report, I also cannot reproduce the duplication issue. I have successfully duplicated more than 1 products from the original product. |
@magento-engcom-team give me test instance |
Please reopen PR ^ when this one is merged. |
Closing this PR. We will move this PR to magento/magento2 repository |
Hi @pogster, thank you for your contribution! |
Description
This PR may replace #102.
In contrast to the original PR I restored the SKU autogeneration in case a product is duplicated. The product copier will copy the original SKU and save the duplicate in a loop until a unique url key is found - if no SKU is autogenerated and no valid SKU is supplied it simply won't save the product.
Since the copier sets "isDuplicate" = true I thought it would be good simple solution to check for that entry before autogenerating a SKU.
Fixed Issues (if relevant)
Manual testing scenarios
Contribution checklist