The README.md suggests that api.Products.iterall() and api.Products.count() should exist but they do not appear to.
Also, the releases page says that the last release was 2019. They're haven't been any substantial updates since then?
Also, the forum entry at #59 says the following:
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.
The README.md suggests that
api.Products.iterall()andapi.Products.count()should exist but they do not appear to.Also, the releases page says that the last release was 2019. They're haven't been any substantial updates since then?
Also, the forum entry at #59 says the following:
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.