-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: init
to depend on add.Configure
#4698
Conversation
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
I see, so previously |
@rajeshkamal5050 Thanks for asking! The code sharing is mostly in the prompting logic. In my mind, both packages are app-level packages, and I'm avoiding introducing additional layers or packages for "resharing prompting logic" right now, we'll break it down later if needed. We did reshare library components between them (such as the |
This change reshares UI prompting logic between
init
andadd
.Context
init
logically depends onadd
since it is essentially a quick wizard that ends up prompting attributes for each resource. In the limit,init
can be thought of as a series ofadd
calls, though this is not reflected in practice due to difference in UX design considerations.This is a pure refactor and does not introduce any functional changes. The UI prompting is covered by existing tests.