Is there a reason we're not using model.Product here? There's already so many different product types I feel like it's gonna cause a problem down the line. Alternatively we can delete model.Product, since it really is just a copy of ps_product database type. (The latter sounds like a good thing to do)
idk if we want to keep a close eye on the returned errors? Because most files return responseErrors.ErrInvalidBody when localeExtractor fails. Similarly, when attribute can not be parsed, most handlers return esponseErrors.ErrBadAttribute.
Okay, so I looked at most of it, basically excluding specificPriceRepo.go and sql procedures.
There's additional issue with indexes in create_tables. We have:
CREATE INDEX idx_bsp_customer ON b2b_specific_price_customer (b2b_specific_price_id, b2b_id_customer);
but b2b_specific_pric…