You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @sabotagebeats, the pagination values you're referring to come from the V3 BC API, whereas this library is for the older V2 API and has not yet been updated for V3.
Has V3 been since released?
Lastly, when I call (api).Products.all() for some page equal-to-or-greater-than the page-count (the page after the last page of results), I get a single string with a value of "_connection" back. So, when there are products, we get a Product. Otherwise, we get a string with "_connection". I would expect an empty result or, at worst, a None. Can you explain what's going on here? How is pagination supposed to work? I'm having issues finding documentation and what little documentation is available (above) seems broken or inaccurate. Since the source-code is reflective, there are no clues there, either.
I tried following the v3 update at #86 under the "Files changed" tab to add v3 compatibility, but I'm getting a 401 due to X-Auth-Client and X-Auth-Token headers not working as they do with the v2 api_path. Have you tried adding the extra code from #86? I can't help with any of the other issues though, sorry.
Activity
argoapps commentedon May 14, 2021
I tried following the v3 update at #86 under the "Files changed" tab to add v3 compatibility, but I'm getting a 401 due to X-Auth-Client and X-Auth-Token headers not working as they do with the v2 api_path. Have you tried adding the extra code from #86? I can't help with any of the other issues though, sorry.