Chinesezjc
b462d5fd69
Adapt to two contract changes master introduced: - The generated Remote face now wraps every business result in RemoteResult, folding carrier failures into an ok:false branch instead of rejecting. The controller reads that envelope at its three call sites and maps a carrier failure onto the same settled shape the controls already render; three specs cover the new branch. - Client packages split their tsconfig into host and client halves, and the host aggregate now compiles any test not named *.client.spec.*. Rename this package's specs to the client convention and drop the ../connection project reference, which pointed at a solution file that no longer carries the client sources. Keep master's mount loop with its rollback-on-failure in api-remotes and add messageFeedbackRemote to it.
19 lines
716 B
TypeScript
19 lines
716 B
TypeScript
/** Shared loopback-hostname semantics for the Host fence and browser UI. */
|
|
|
|
import { describe, expect, it } from 'vitest'
|
|
import { isLoopbackHostname } from '../src/loopback-hostname.ts'
|
|
|
|
describe('isLoopbackHostname', () => {
|
|
it('accepts localhost, IPv6 loopback, and the whole IPv4 127/8 block', () => {
|
|
for (const hostname of ['localhost', '[::1]', '127.0.0.1', '127.8.9.10', '127.255.255.255']) {
|
|
expect(isLoopbackHostname(hostname)).toBe(true)
|
|
}
|
|
})
|
|
|
|
it('refuses malformed and non-loopback hostnames', () => {
|
|
for (const hostname of ['remote.localhost', '::1', '128.0.0.1', '127.0.0', '127.0.0.256', '127.0.0.-1']) {
|
|
expect(isLoopbackHostname(hostname)).toBe(false)
|
|
}
|
|
})
|
|
})
|