4 Commits

Include renames

Author	SHA1	Message	Date
Conrad Irwin	a675ca7a1e	Remove into SelectionEffects from .change_selections (#33554) ... In #32656 I generalized the argument to change selections to allow controling both the scroll and the nav history (and the completion trigger). To avoid conflicting with ongoing debugger cherry-picks I left the argument as an `impl Into<>`, but I think it's clearer to make callers specify what they want here. I converted a lot of `None` arguments to `SelectionEffects::no_scroll()` to be exactly compatible; but I think many people used none as an "i don't care" value in which case Default::default() might be more appropraite Closes #ISSUE Release Notes: - N/A	2025-06-27 14:31:31 -06:00
Conrad Irwin	6e762d9c05	Revert "Remove into SelectionEffects from .change_selections" ... This reverts commit 28380d714d.	2025-06-27 14:06:17 -06:00
Conrad Irwin	28380d714d	Remove into SelectionEffects from .change_selections ... In #32656 I generalized the argument to change selections to allow controling both the scroll and the nav history (and the completion trigger). To avoid conflicting with ongoing debugger cherry-picks I left the argument as an `impl Into<>`, but I think it's clearer to make callers specify what they want here. I converted a lot of `None` arguments to `SelectionEffects::no_scroll()` to be exactly compatible; but I think many people used none as an "i don't care" value in which case Default::default() might be more appropraite	2025-06-27 14:03:45 -06:00
Max Brunsfeld	2283ec5de2	Extract an agent_ui crate from agent (#33284) ... This PR moves the UI-dependent logic in the `agent` crate into its own crate, `agent_ui`. The remaining `agent` crate no longer depends on `editor`, `picker`, `ui`, `workspace`, etc. This has compile time benefits, but the main motivation is to isolate our core agentic logic, so that we can make agents more pluggable/configurable. Release Notes: - N/A	2025-06-23 18:00:28 -07:00