Skip to content
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

[Dev Drive Insights] Prepopulate the file path for moving caches #2681

Closed
joadoumie opened this issue Apr 18, 2024 · 1 comment · Fixed by #3287
Closed

[Dev Drive Insights] Prepopulate the file path for moving caches #2681

joadoumie opened this issue Apr 18, 2024 · 1 comment · Fixed by #3287
Assignees
Labels
Area-DevDriveInsights Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Issue-Task Feature request that doesn't need a major design Resolution-Fix-Available Available in a release

Comments

@joadoumie
Copy link
Contributor

Suggested new feature or improvement

When suggesting that users move their caches, it'd be nice to prepopulate the most sensible file path for the user so they don't have to browse and create a new folder or type in a new path. The default should be what is shown in the example.

Scenario

Make it more seamless for users to move their package caches.

image

Additional details

No response

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Apr 18, 2024
@kanismohammed kanismohammed removed the Needs-Triage New issue that the core contributors need to triage label Apr 25, 2024
@zadjii-msft
Copy link
Member

I also don't think that it'll let you "make changes" unless you actually "Browse" first. If you just type the path in, you need to still Browse to that same path:
image

@cinnamon-msft cinnamon-msft added Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Issue-Task Feature request that doesn't need a major design and removed Issue-Feature New feature or request labels Jun 13, 2024
@krschau krschau added the Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release label Jul 8, 2024
@krschau krschau added this to the Dev Home v0.16 milestone Jul 8, 2024
@krschau krschau added Resolution-Fix-Available Available in a release and removed Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release labels Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-DevDriveInsights Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Issue-Task Feature request that doesn't need a major design Resolution-Fix-Available Available in a release
Projects
None yet
7 participants