Open pdushkin opened 12 years ago
Hi guys,
I'll need to get a bit more context to understand the problem. What is "merge listing"? I tried to catch up on the previous discussion and it seems to be related to merging "marketplace authorisation" and "listing creation" into a single call?
I think that we need to distinguish several things here:
When creating a listing, the user can select a subset of the authorised marketplaces for listing this item. This could be done using a single or multiple API calls:
a) if it is a single call, it would take a variable number of parameters because the parameters passed in would depend on the selected marketplaces
b) if it is multiple calls, we would have a single call for creating a Libereco listing and individual calls for creating the same listing on additional marketplaces, passing in the extra parameters needed for that specific marketplace.
All of this could be made transparent from the perspective of the mobile client application because it would just be issuing REST calls as the users completes the UI screen for authorising marketplaces, creating listings etc
I had a look at the code but it'll be quicker if you can point me to the right branch, so I can look at the current REST API to understand the problem better.
From a UX point of view, it seems to be important that a user can delist from a single marketplace after listing creation (without changing authorisation).
What do you think?
Cheers, Peter P
Now that we are going for merge listing it would not be possible to perform action on single marketplace. For example, if a user wants to delist his item from Ebay but not Etsy how would we support it. In the merge listing approach we are having a single entity(LiberecoListing) which will have data for all marketplaces. So, rest web services will be exposed over libereco listing object.