-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Remove long form name behavior for pubsub subscriptions #4508
Comments
I forget the exact context, but we have custom code to allow specifying something- I think the Edit: Actually, I think the field was |
|
Ah- yep, I think that was it. |
Cool. Since @c2thorn has plenty of other things on his plate right now, I'm going to go ahead and take this since it's pretty quick. |
Closed in linked issue ("Fixes: " doesn't work in non-primary branches) |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
I'm not sure on the background of this one, but it came up in our discussion of 3.0.0 goals. I believe you can currently specify two versions of the pubsub subscription name, and the long one is undesirable for some reason, and so we want to stop supporting it. @danawillow, assigning this to you so you can assign it to Cameron when they get commit access.
The text was updated successfully, but these errors were encountered: