feat: resolve and render dotNS names under each network's TLD - #159
Conversation
⚡ Performance Report
|
Bundle Size ReportChunks over 500 KB:
All files
Commit: 700d8ac |
|
This is a Nova-side outage and not a dot.li test failure. Re-run Logs: https://github.com/paritytech/dotli-community/actions/runs/31616965661 |
|
@justraman just waiting for truapi to release a new version so we don't include the vendor folder. or |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
❌ E2E Product suite failed on Failed tests:
Logs: https://github.com/paritytech/dotli-community/actions/runs/31732448160 |
Summary
TLDto each network'sdotnsconfig (paseofor Paseo Next V2,dotfor the others) plusgetActiveTld,getActiveTldSuffix,withActiveTld, andstripActiveTldhelpers, and routes the resolver, URL parser, product-id mapping, and every user-visible label through them.productIdagainst a hardcoded.dot, so it rejects every.paseoproduct.vendor/truapi-host-wasm/carries the 0.4.0 core rebuilt with the fix from fix: accept per-network dotNS TLDs in product identifiers host-rust-core#369, andapps/host/vite.config.tsprefers it.