test(ui): did-wallet launch port follows its manifest (8088)
All checks were successful
Demo images / Build & push demo images (push) Successful in 2m49s
All checks were successful
Demo images / Build & push demo images (push) Successful in 2m49s
The pine catalog regeneration (c1dfc667) refreshed generatedAppSessionConfig from the manifests, where did-wallet publishes host port 8088 — the test's 8083 expectation was stale. The test asserts manifest-generated ports are used, so it must track the manifest. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
ea80815c98
commit
4bac839fb3
@ -33,7 +33,10 @@ describe('appSessionConfig', () => {
|
||||
configurable: true,
|
||||
})
|
||||
|
||||
expect(resolveAppUrl('did-wallet')).toBe('http://192.168.1.228:8083')
|
||||
// did-wallet's manifest publishes host port 8088 (apps/did-wallet/
|
||||
// manifest.yml) — assert against the manifest-generated value, which is
|
||||
// exactly what this test exists to protect.
|
||||
expect(resolveAppUrl('did-wallet')).toBe('http://192.168.1.228:8088')
|
||||
})
|
||||
|
||||
it('does not treat service-only tcp ports as web launch surfaces', () => {
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user