CodeVetter · Repo Unpack · Extension points
testing-library/dom-testing-library
The library exposes factories and wrappers as extension mechanisms for consumers and framework adapters. Query families plug into export tables, and custom query maps can be bound without modifying the default registry. Event shortcuts derive from a declarative map, while configuration injects scheduling, dispatch, and diagnostic behavior. Public declarations form a parallel extension contract that must remain aligned with runtime behavior.
- New built-in query families plug into src/queries/index.ts; that namespace feeds the public entrypoint and screen, so its runtime exports must remain query functions.
- buildQueries accepts an all-query plus multiple/missing error functions and produces five variants; Text illustrates this pattern, while LabelText deliberately assembles variants separately for richer errors.
- getQueriesForElement accepts a custom function map and optional initial object; consumer tests demonstrate extending default queries, and type fixtures bind a custom AutomationId family through within.
- queryAllByAttribute supplies normalized attribute matching, while exported makeSingleQuery, makeGetAllQuery, makeFindQuery, and suggestion wrappers allow custom composition below buildQueries.
- configure injects asyncWrapper, unstable_advanceTimersWrapper, and eventWrapper; waitFor and fireEvent invoke these hooks, and source comments identify framework act integration as their purpose.
- eventMap entries define constructor type and default initialization, automatically generating createEvent/fireEvent methods; eventAliasMap supplies alias dispatch such as doubleClick.
- Diagnostics can be customized through configure.getElementError, prettyDOM's filterNode and pretty-format options, and waitFor's onTimeout/mutationObserverOptions; these hooks affect failure output and retry observation.
- Matcher functions and normalizers customize matching, but normalizer cannot be combined directly with trim/collapseWhitespace; type-level extension uses QueryMethod, BuiltQueryMethods, and BoundFunctions to preserve custom argument and result types.