-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Improve configure user experience #3158
Conversation
This comment has been minimized.
This comment has been minimized.
|
||
if (messageData.ShowDescription && !description.empty()) | ||
{ | ||
constexpr size_t maximumDescriptionLines = 3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be nice if users could configure this. Maybe just a TODO for now until we know if being able to configure would be useful
// Required Args: ConfigurationFile | ||
// Inputs: None | ||
// Outputs: None | ||
void EnsureConfigurationFileExists(Execution::Context& context); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This name of this almost makes me think that this could be abstracted into a generic check for files existing where an enum could provide the logic of which arg to grab the path from . winget import
is one that comes to mind, install/uninstall/show with --manifest
, winget hash
, etc. I'm surprised this isn’t genericised already. . .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It actually is, and I wrote it. I just didn't look hard enough to rediscover VerifyFile
.
Change
This change improves the
configure
user experience by:configure
command.Details
property is not empty.It also logs the entire configuration file input stream to the log in verbose, and improves the progress reporting for the pre-check of the apply flow.
The initialization phases are reported as:
Validation
Only minor manual validation has been done at the time of PR creation.
Automated testing should certainly be added, but we may want to forego that at this time given how poor the current UX is and the desire to get a build out for testing.
Microsoft Reviewers: Open in CodeFlow