mirror of
https://github.com/zed-industries/zed.git
synced 2025-01-11 05:00:16 +00:00
cbe7a12e65
I'd love to take on fixing this but: 1. I don't think this is the right solution - it would be really nice to have something actionable that I could do when presented with this message. 2. Should signing in to Copilot be independent from whether it's enabled? You can only access the sign-in modal when `features.copilot` isn't disabled, but when `show_copilot_suggestions` is `false` the server is disabled but you can't sign in. So I guess another solution might be to just not show the UI if copilot suggestions are disabled? 3. I don't know what other circumstances could trigger the empty modal. I see `Status::Error` and that seems like it might be important to surface gracefully? Would love some thoughts on this Release Notes: - Improved UX for enabling Copilot when it's disabled in settings |
||
|---|---|---|
| .. | ||
| copilot_button.rs | ||
| copilot_ui.rs | ||
| sign_in.rs | ||