Skip to content

Conversation

jgallagher
Copy link
Contributor

No description provided.

Copy link
Collaborator

@davepacheco davepacheco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change itself is fine but I'm not sure how we want to deal with:

  • this version may drift over time
  • someone could break this API without realizing there's a bash consumer out there (nothing would break at CI-time)

Maybe the switch zone should ship a Rust binary using a Progenitor client that does this? This way:

  • the program would automatically pick up new changes to the API
  • things would break at build-time if the API were broken
  • ls-apis would see this consumer

If that makes sense to you, maybe just file an issue about it for now? I think we could tag it good-first-issue.

@jgallagher
Copy link
Contributor Author

If that makes sense to you, maybe just file an issue about it for now? I think we could tag it good-first-issue.

It does! Filed #8976.

@jgallagher jgallagher merged commit 71f1965 into main Sep 3, 2025
16 checks passed
@jgallagher jgallagher deleted the john/fix-switch-zone-shell-prompt branch September 3, 2025 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants