fix: enforce rollout gates across backend entry points
This commit is contained in:
@@ -13,11 +13,12 @@ describe('deployment rollout gate', () => {
|
||||
expect(baseline).toEqual(BASELINE_RELEASE_CAPABILITIES);
|
||||
expect(capabilityEnabled('asset_search', baseline)).toBe(true);
|
||||
expect(capabilityEnabled('wallet_balance', baseline)).toBe(false);
|
||||
expect(capabilityEnabled('subscriptions', baseline)).toBe(false);
|
||||
expect(capabilityEnabled('subscriptions', baseline)).toBe(true);
|
||||
});
|
||||
|
||||
test('supports explicit narrowing and rejects unknown or empty names', () => {
|
||||
expect(parseCapabilityAllowlist('asset_search, asset_search,session_token')).toEqual(['asset_search', 'session_token']);
|
||||
expect(parseCapabilityAllowlist('subscriptions')).toEqual(['subscriptions']);
|
||||
expect(parseCapabilityAllowlist('')).toEqual([]);
|
||||
expect(() => parseCapabilityAllowlist('asset_search,typo')).toThrow('Unknown deployment capability');
|
||||
expect(() => parseCapabilityAllowlist('asset_search,')).toThrow('Unknown deployment capability');
|
||||
|
||||
Reference in New Issue
Block a user