Repository navigation
Keep WooCommerce order lists small and state weclapp's sort syntax - #1619
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two adapter definitions led models into slow or failing calls on Cloud (2026-11-09 daily check):
list_ordersreturns complete orders. Atper_page100 that is 5 to 9 MB per call: one workspace made 180 such calls in a day (865 MB, 8.2 s each on average) and 21 of the day's 104 event-loop stalls over 1 s came right after its bursts; another workspace timed out at 31 to 38 s. The tool offered no way to trim the response and no page-size guidance.sortonly said "Sort field, prefix with '-' for descending". Models sentinvoiceDate:descor fields the record does not have (bookingDateon stock movements), about 25 of 53 weclapp errors across 8 workspaces.Changes
intl/woocommerce.json:woocommerce_list_ordersandwoocommerce_search_productsget WordPress's_fieldsquery parameter (optional, empty = complete records, so nothing changes for existing callers) and aper_pagedescription that recommends 20 to 50.list_orderssays to read one complete order withwoocommerce_get_order.de/weclapp.json: thesortdescription on all 25 list tools states the syntax (bare field name,-for descending), saysfield:descfails, and gives an example that exists on that record (-invoiceDatefor invoices,-postingDatefor stock movements,-createdDateelsewhere).Cloud and self-hosted behave the same. The new
_fieldsparameter changesendpointMapping, so installed WooCommerce connectors get it after "Apply update"; the descriptions sync on their own.Type
Testing
Definition-only change; the static catalog specs cover it. From the repo root:
node scripts/validate-adapters.mjs --warn(no new warning for these tools),node scripts/regenerate-catalog.mjs(catalog.ts unchanged),node scripts/adapter-count.mjs --check(OK, 730 adapters). Inpackages/backend:npx jest src/adapters/de/weclapp.spec.tsand the WooCommerce static specs pass; the full suite runs in CI (local Prisma client was out of date for unrelated suites).Checklist
npm test) (CI)Related Issues
Found in the 2026-11-10 daily check (Cloud tool errors and event-loop stalls).