other write-ups say default sort keeps returning page 1, while explicit sorts like popularity, price_asc or new paginate properly. cursor walking may be fine, but the /search path is your wrapper’s endpoint, so the behavior probably comes from your implementation and not myntra itself
btw worth mentioning the sort parameter alongside the cursor so we know the default can loop
coupon_discounted_price should state its scope, whether that’s a coupon code, a cart minimum or a per-user price. average_rating as a string is a small inconsistency next to the numeric prices so normalizing it to a number would make the schema cleaner
On the pagination, that one is Myntra’s own behavior, not my wrapper. Myntra’s search is cursor-based internally. Each response hands you back a context token and you pass that token into the next call to get the next page. If you don’t carry that token, Myntra just keeps giving you page 1 on the default sort, which is most likely the page-1 loop those other write-ups are running into. My /search walks that same Myntra cursor, so it pages through properly. You can check it yourself by hitting Myntra’s own search call without the context token and you’ll see it loop too. Using an explicit sort like popularity or price_asc is really just another way around the same Myntra behavior. Good shout on calling it out though, I’ll make the default-loop thing clear in the docs.
On coupon_discounted_price, that’s the final price you actually pay after the maximum discount on the product is applied, not a coupon code or cart-minimum thing. I’ll spell the scope out in the docs so it’s not ambiguous.
On average_rating, yeah. It should be a number like the prices are, so I’ll normalize it to keep the schema consistent.
OnlineProxy
other write-ups say default sort keeps returning page 1, while explicit sorts like popularity, price_asc or new paginate properly. cursor walking may be fine, but the /search path is your wrapper’s endpoint, so the behavior probably comes from your implementation and not myntra itself
btw worth mentioning the sort parameter alongside the cursor so we know the default can loop
coupon_discounted_price should state its scope, whether that’s a coupon code, a cart minimum or a per-user price. average_rating as a string is a small inconsistency next to the numeric prices so normalizing it to a number would make the schema cleaner