justin/new-site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(dexit): note NV adapter also mis-parses happy path (not just errors)

Browse source
This commit is contained in:
justin 2026-06-09 08:14:09 -05:00
parent 76c4d55603
commit 561ad78ea8
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/dexit-readiness-assessment.md
View file

@ -57,8 +57,12 @@ input selector, and `search_name()` swallows the exception and **defaults to
- This is a **portal-scraping maintenance task**: inspect the current NV (and verify
TX) name-search DOM, update `states/nv/adapter.py` (and `tx`) selectors/flow, and
make `search_name()` distinguish a real "taken" result from an adapter error
(return an explicit error/unknown state, never a false "taken"). The harness
re-run is the acceptance test.
(return an explicit error/unknown state, never a false "taken"). NOTE the adapter
also MIS-PARSES on its happy path: via the route a unique name still returns
available=false (the search page content does not match the adapter's "no results"
phrases), so the fix must update both the input selector AND the results parsing.
We did harden the error path: search_name() now returns available=None on a thrown
adapter error. The harness re-run is the acceptance test.
**Conclusion:** the ERPNext/order plumbing is sound and verified; **do not enable a
self-serve formation checkout until name search is fixed** (a customer must be able