Describe the bug
Call ng add. Resource group is created and spinner gets stuck early on. Having tracked down the issue it's in the checkNameAvailability() function. The function is meant to validate a name and needs to respond true if name is available and false if not. Currently, it gets stuck in a loop of false responses
Suggested code fix is
return async (account: string) => {
spinner.start();
const availability = await client.storageAccounts.checkNameAvailability(account);
if (!availability.nameAvailable && warn) {
spinner.fail(availability.message || 'chosen name is not available');
return false;
} else {
spinner.stop();
return true;
}
};
}
Expected behavior
Expect azure.json to be generated
Describe the bug Call ng add. Resource group is created and spinner gets stuck early on. Having tracked down the issue it's in the
checkNameAvailability()
function. The function is meant to validate a name and needs to respondtrue
if name is available andfalse
if not. Currently, it gets stuck in a loop offalse
responsesSuggested code fix is
Expected behavior Expect
azure.json
to be generated