In Existing Implementation, Compare Lis doesn't have an id on its own. Its state is tied to Luma's session which should not be the case for GraphQl. Every new list entry expects a visitor_id in the database which is from Visitor session and cannot be mocked.
Existing proposal expects clients to generate list_id (Compare list id). This idea is debatable and can lead to data inconsistency.
Solution
Establish a list_id for each of the compare list. Clients will be able to create compare list to get a list_id. list_id can be used for future operations on the compare list
Problem
Solution
Requested Reviewers
@akaplya @melnikovi @cpartica @DrewML @nrkapoor @mauragcyrus